Page History

...

• 1a - Source conformant to m2 standards (files and packages) + tweak build.xml
  1. This was checked-into svn:fedora/trunk.rev.8076
  2. The basic structure of maven has been created (src/main/java, src/test/java, etc)
  3. 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
  1. Based on the jars in the /lib dir, a simple install script pushes them into the local repository
  2. Need to create proper *.pom and <dependency> for each artifact
• 2 - Ant-maven integration (two four subprojects) with main goal of installer.jar
  • This initial integration requires
  3 - m2-only (initial split-out)
  • a minimum break-out of the following subprojects
  • repository
    1. This currently is the bulk of the source-code
  • soap
    1. common
       • This contains 'fedora.common' package
    2. generated
    1. • This is the code generation project, all within the context of web-services/soap
       • wsdl2java generation and stubwrappers
    2. utilities
    3. repository
       • This currently is the bulk of the source-code
• 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

...

1. Currently, all of the maven dependencies are in the top-level pom.xml
   1. They need to be surgically pushed down to their approapriate subproject pom.xml
   2. Their dependency declaration needs to point to the proper version on maven-central, not the locally created artifact
2. The continued need for each junit suite aggregator class needs to be re-evaluated
3. Unit test naming conventions need to be standardized (since maven invokes them based on a regex at different build phases)
   1. unit-test: '**/*Test.class'
   2. integration-test: '**/Test*.class'