Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "JWT DeveloperFAQ"
m (→Adapting the Eclipse Update Site) |
m (→Internal Layout of the JWT Source Code) |
||
| Line 6: | Line 6: | ||
== Internal Layout of the JWT Source Code == | == Internal Layout of the JWT Source Code == | ||
| + | |||
| + | === Workflow Editor === | ||
| + | |||
| + | * ToDo | ||
== How to Extend/Modify JWT == | == How to Extend/Modify JWT == | ||
Revision as of 11:17, 28 July 2008
Frequently Asked Questions for Developers
Contents
Installing JWT Source Code from CVS
For information on how to access the JWT source code, the layout of the CVS repositories and the dependencies of JWT components, please refer to JWT CVS Information.
Internal Layout of the JWT Source Code
Workflow Editor
- ToDo
How to Extend/Modify JWT
Extending the Workflow Editor
The article Extending JWT-WE contains information on how JWT can be extended by user-defined plugins that provide e.g. external actions or additional views.
Modifying the Workflow Editor
The article Modifying JWT-WE provides information on how several recurring tasks (like adding preferences to the preferences menu) can be accomplished.
How to prepare a new Release
Releasing the Workflow Editor
1. Preparing
- Make sure the copyright/year information in the Java headers is up to date
- Adjust plugin*.properties translations
- Remove unneccessary dependencies using the Plugin.xml editor
- Make sure the description of the JWT extension points is up to date
- Close finished Bugzilla tasks and move open ones to next release
- Update the internal documentation in JWT-WE (about.txt, package.html)
- Make sure the internal version of the Workflow Editor and all its plugins is set to the new release version
- The converter must be updated to the newest file format
- Ensure that all keybindings for Eclipse commands (menu/toolbar) are set correctly
- Make sure the licence information is valid
- The internal readme file must be up to date
- Update the release notes
2. Generating Packages
- Generate new Javadoc
- Generate a release package and a source package for the Workflow Editor
- Generate a release package and a source package for the WE View Creator
- Generate release and source packages for all WE Plugins
- Update the example processes and create a ZIP archive
- Sign packages
3. Deploying
- Tag the release state on the CVS as a new version
- Archive old release and upload new release packages to the download server
- Update the Wiki download page and related Wiki pages
- Update the Eclipse JWT page
- Adapt the feature in the JWT Eclipse Update Site
- Notify Mailing List
Releasing the AgilPro LiMo/Simulator
- update release notes
- update tutorial
- update javadoc
- update howtos
- update install informations
- valid licence in installer?
- valid update splashscreen?
- copy emf model to simulator
- convert sample processes
- test installer for all operating system versions
- SVN: branch, javadocs
- CVS: tag version
- mylyn: close finished bugs, move open ones to next release
Preparing
Generating Packages
Deploying
Eclipse Maintenace Stuff
Putting Files on the Download Server
- Old files should be moved to archive.eclipse.org:
- ssh yourcommitterid@dev.eclipse.org
- mv ~/downloads/your/project/oldrelease/ /home/data/httpd/archive.eclipse.org/your/project/oldrelease/
- Connect to download1.eclipse.org using SCP/SFTP and upload the new files
- Update the JWT Download Site
- Update the main JWT site (news area, download area)
Updating the Web Site
- Connect to the CVS repository /cvsroot/org.eclipse on dev.eclipse.org
- The files concerning the JWT page are in the directory /www/jwt
- Refer to http://www.eclipse.org/phoenix/ for information on how to set up the pages
Adapting the Eclipse Update Site
- ToDo