...
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 seperatedseparated. This means that the ANT builds must continue to work as the baseline becomes incrementally transformed.
...
- Currently, all of the maven dependencies are in the top-level pom.xml
- They need to be surgically pushed down to their approapriate 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
...
During this initial conversion to Maven2, we want to minimize the degree of baseline upheavel upheaval while splitting out subprojects enough to allow maven to properly function.
...