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
• 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
    1. generate
       • This is a small project that creates the executable stubwrapper generator
    2. common
       • This contains 'fedora.common' package
       • includes wsdl2java generation and stubwrappers
       • has dependencies on '/generate'
    3. server
       • This is the 'fedora.server' package
       • has dependencies on '/common'
    4. client
       • This is the 'fedora.client' package
       • has dependencies on both '/common' and '/server'
    5. integrationtest
       • This is the 'fedora.test' package
       • has dependencies on both '/client' and '/server'
    6. localservices
       • This contains three sub-projects
         • fop
         • imagemanip
         • saxon
       • War files are created for all contained sub-projects when running mvn clean install
    7. democontent
• 2b - All maven unit tests (test inventory)
  • This was checked-into svn:fedora/trunk.rev.8086
  1. generate
  2. common
  3. server
  4. client
  5. 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
  1. generate
  2. common
  3. server
  4. client
  5. integrationtest
• 2d - All maven system tests (test inventory)
  • These tests run within the 'integrationtest' project as separate profiles.
  • This was checked-into svn:fedora/trunk.rev.8088
  1. ConfigA
     • mvn clean install -P configA
  2. ConfigB
     • mvn clean install -P configB
  3. ConfigQ
     • mvn clean install -P configQ
• 2e - installer.jar (and other artifacts verified)
  1. client.jar
     • This is being created with the default build target: (mvn package)
     • Its artifact name contains the 'fedora' classifier (see note below for todo)
  2. installer.jar
  3. rmi-journal-receiver.jar
  4. fedora-demo.war (democontent)
  5. local-services
     • This was checked-into svn:fedora/trunk.rev.8092
     1. fop.war
     2. imagemanip.war
     3. saxon.war
  6. api.jar
     • Is this still used?
  7. messaging-client.jar
  8. messaging-client.zip
  9. fedorahome.zip
  10. fedora.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

...