...
- 1a - Source conformant to m2 standards (files and packages) + tweak build.xml
- 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
- 2a - Ant-maven integration (five subprojects) generating source and building
- This initial integration requires a minimum break-out of the following subprojects
- This is just building, unit tests turned off
- This was checked-into svn:fedora/trunk.rev.8083
- generate
- This is a small project that creates the executable stubwrapper generator
- common
- This contains 'fedora.common' package
- includes wsdl2java generation and stubwrappers
- has dependencies on '/generate'
- server
- This is the 'fedora.server' package
- has dependencies on '/common'
- client
- This is the 'fedora.client' package
- has dependencies on both '/common' and '/server'
- integrationtest
- This is the 'fedora.test' package
- has dependencies on both '/client' and '/server'
- generate
- 2b - All maven unit tests (test inventory)
- This was checked-into svn:fedora/trunk.rev.8086
- generate
- common
- server
- client
- integrationtest
- No unit tests here by definition
- 2c - All maven integration tests (test inventory)
- Like the system tests previously provided in the ANT tests (ConfigA/B/Q), for now, the Maven2 integration tests will require a pre-started application server.
- Because integration tests are run during the default build lifecycle of Maven2, you must pass the following flag at build-time to disable the running of integration tests ('integration.test.skip')
mvn clean install -Dintegration.test.skip=true
- generate
- common
- server
- client
- integrationtest
- 2d - All maven system tests (test inventory)
- ConfigA
- ConfigB
- ConfigQ
- 2e - installer.jar (and other artifacts verified)
- client.jar
- installer.jar
- (!) rmi-journal-receiver.jar
- (!) local-services
- fop.war
- imagemanip.war
- saxon.war
- 3 - m2-only (full split-out)
- Admin Client
- Java Client API
- Server Webapp
- Installer
- (Old GUI)
- New GUI
- 4 - Split out server modules as projects
- 5 - Rename packages based on Maven-central's requirements
...