Page History

...

• *# This was checked-into svn:fedora/trunk.rev.8076
  1. The basic structure of maven has been created (src/main/java, src/test/java, etc)
  2. 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 subprojects) with main goal of installer.jar
  • This initial integration requires
• 3 - m2-only (initial split-out)
  • repository
    1. This currently is the bulk of the source-code
  • soap
    1. This is the code generation project, all within the context of web-services/soap
    2. wsdl2java generation and stubwrappers
  • 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

To Revisit

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