The Release Engineering component currently does not contribute any plug-ins.
Tools
As of build I20040420, the RelEng Plug-in is included in the Eclipse builds
and is available at the bottom of the download page.
RelEng Plug-in 3.0.4
(For builds > 20040622)
RelEng Plug-in
3.0.3 (For builds I20040302 and after)
RelEng
Plug-in 3.0.2 (For builds after I20040204)
RelEng
Plug-in 3.0.0 (For builds after I20031113)
RelEng
Plug-in 2.1.0 (For builds after N20030630)
RelEng
Plug-in 2.0 (For builds before N20030630)
This Plug-in provides features that will help with the Eclipse development process. Installing the plug-in will add the following actions. The source is contained in the *.jar files so please feel free to submit patches for features you think would be cool. To install simply unzip the file into your plugins directory and restart Eclipse. Please use the Release feature of this plug-in to do your build submissions.
- Release to the Team menu. This action will Tag selected projects with the specified version and update the appropriate loaded *.map files with the version. The user must have the *.map files loaded in their workspace and the use must commit the map file changes to the repository when done.
- Load Map Projects to the Team menu. Select one or more *.map file and this action will load the projects listed in the *.map file into your workspace. Naturally the versions specified in the *.map file will be loaded.
- Tag Map Projects to the Team menu. Select one or more *Map files and this action will tag the projects listed in the *Map files with a tag you specify.
- Compare with Released to the Compare menu. Compare the selected projects with the versions referenced in the currently loaded map files.
- Replace with Released to the Replace menu. Replace the selected projects with the versions referenced in the currently loaded map files.
- Fix Copyright to the Resource Perspective Projects context menu. Select one or more projects in the Resource Perspective. This action will sanity check the copyright notices in all the *.java and *.properties files. Copyrights will be updated automatically where the tool deems appropriate. A copyright.log file will be written to the workspace directory noting odd conflicts that need to be looked at. You need to commit the changes yourself. This is the tool that was used to do the 2.1 Copyright pass.