...
- Maintenance Developers (May need to work on features that effect all of the source)
- Trunk-all is an external that has everything in it. For now, just use that:
- Soon there may be a 'Sakai Core (like cafe)' and a 'Sakai Options (indies)' which would require 2 checkouts
- From this you can just run "mvn clean install"
- Additional options include
- (Pack Profiles) -Ppack-demo, -Ppack-bin, -Ppack-src, -Ppack (does all 3)
- (Sakai deployment) sakai:deploy -Dmaven.tomcat.home=/some/directory/to/deploy/to
- (Skip tests) -Dmaven.test.skip=true
- TODO: Document or find documentation about core-deploy for local deployers who want to customize their build
- Single (minimal) Tool Developers (Working on a single Sakai tool)
- The easiest way is to just convert your tool to an indie with a pure-poms parent. You don't need any other code.
- For a new tool, you may want to use the Sakai Wicket Maven Archetype
- You can use the same build options as Maintenance Developers (mvn clean install + options)
- TODO: Provide link to converting tool to indie and some documentation about purepoms
- TODO: Provide link to current javadocs for kernel and other tools
- Release Team (The group that actually needs to package and release the next version of Sakai)
- The release team will have to check out and release each tool as needed and release it. We're working on a way to automate this. Stay tuned!
- Ideally the maven release:prepare task will be automated, or dependent modules will be automatically versioned.
- Release Management Documents
- TODO: Document the release process better
...
Additional tips and tricks
...