...
- Currently, all of the maven dependencies are in the top-level pom.xml
- They need to be surgically pushed down to their appropriate subproject pom.xml
- Their dependency declaration needs to point to the proper version on maven-central, not the locally created artifact
- The continued need for each junit suite aggregator class needs to be re-evaluated
- Unit test naming conventions need to be standardized (since maven invokes them based on a regex at different build phases)
- unit-test: '**/*Test.class'
- integration-test: '**/Test*.class'
- All unit/system/integration tests used to fall under 'fedora.test'
- now that they have been split across subprojects ('server', 'client', 'integrationtest'), they are not aggregated with a single call (i.e. fedora.test.AllUnitTests)
- a fix to this issue would only be needed as long as we continue to use ANT, Maven2 has its own test aggregation
- Build number & timestamp needed for artifact names and manifest files
- The following is a plugin that should do the trick
- It should be configured in the top-level /pom.xml and /client/pom.xml
- http://commons.ucalgary.ca/projects/maven-buildnumber-plugin/index.html
- Refactor fedora.test.FedoraTestCase.java into two classes (one dependent on '/server' and one on '/client') so tests the inherit from it can be pushed back down from '/integrationtest' to their respective projects.
- fedora.test.integration.cma.SimpleDeploymentTests has a bug. See source file for details.
Rationale
Subproject break-out
...