Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Higgins Component Owner Checklist"
(→Component Owners) |
(→Component Owners) |
||
Line 10: | Line 10: | ||
# Owners MUST edit the autobuild scripts to include components in the nightly build | # Owners MUST edit the autobuild scripts to include components in the nightly build | ||
# Owners MUST create a "row" wiki page for each row using the [[Component Description Template]] | # Owners MUST create a "row" wiki page for each row using the [[Component Description Template]] | ||
− | # Owners | + | # Owners MUST make sure that automated build scripts are using the latest build.xml |
==Build Processes== | ==Build Processes== |
Revision as of 15:48, 4 January 2008
Component owners are responsible for creating and maintaining the following wiki doc, build scripts, etc. for their Components.
Contents
Solution Owners
- Solution owner MUST add a link to the solution here Solutions
- Solution owner MUST create the solution page using Solution Description Template
Component Owners
- Owners MUST create rows (and sometimes entire tables) for each project Components page.
- Owners MUST hand create wiki pages in the "Dependencies" column (entitled "Dep.") on the Components page.
- Owners MUST edit the autobuild scripts to include components in the nightly build
- Owners MUST create a "row" wiki page for each row using the Component Description Template
- Owners MUST make sure that automated build scripts are using the latest build.xml
Build Processes
- Component owner MUST use Eclipse 3.3 to define Eclipse projects within component
- Read Eclipse Build Automation
- The owner must ensure that each project (dependencies, etc.) can be managed from within the Eclipse IDE without manually editing build.xml files
- It must be possible for each project to export a build.xml Ant file such that
- It can be used to build all appropriate targets from a command line using CVS and Ant
- It must not use any absolute class names
- It must not require eclipse-specific jar files (only stated dependencies)
- It must build when eclipse is not installed
- It must be able to build both release and debug targets
- Targets
- jar for any consumable component
- war file for WS deployable components
- javadoc
- eclipse plugin
Builds
Nightly
- The component owner is responsible for creating Nightly Component Builds scripts for their component(s).
Stable
- The component owner determines when a build should be promoted from "nightly" to "stable"
- [The higgins project doesn't yet have any "release" builds]