...
The basic strategy was laid out in our last face-to-face committers' meeting in Ithaca.
As you can see, there are a few things that need to be done. If you are interested in helping, I would be very happy to coordinate efforts. Send me an email, Andrew Woods.
Approach
Since moving to Maven2 requires significant restructuring of the baseline directories, we want to make small, incremental changes back to svn/trunk so that the on-going fedora development does become too far seperated. This means that the ANT builds must continue to work as the baseline becomes incrementally transformed.
Progress/Status
Panel |
---|
Not yet |
- This was checked-into svn:fedora/trunk.rev.8076
- The basic structure of maven has been created (src/main/java, src/test/java, etc)
- The renaming of packages based on Maven-central's requirements will happen at the very end of this whole effort
- 1b - Get poms for all dependencies
- Based on the jars in the /lib dir, a simple install script pushes them into the local repository
- Need to create proper *.pom and <dependency> for each artifact
- 2 - Ant-maven integration (monolithic) with main goal of installer.jar
- 3 - m2-only (initial split-out)
- repository
- This currently is the bulk of the source-code
- soap
- This is the code generation project, all within the context of web-services/soap
- wsdl2java generation and stubwrappers
- Admin Client
- Java Client API
- Server Webapp
- Installer
- (Old GUI)
- New GUI
- repository
- 4 - Split out server modules as projects
- 5 - Rename packages based on Maven-central's requirements