Page History

...

1. 1. They need to be surgically pushed down to their appropriate subproject pom.xml
      1. An initial push down is complete though
   2. Their dependency declarations need to point to the proper version on maven-central, not the locally created artifact
      1. All of the artifacts that can be resolved to maven-central without selected new versions is complete
      2. Additional validation is needed especially to ensure that conflicts do not cause problems
   3. Libraries which cannot be resolved to maven-central need to added to the Duraspace Mave repository (under thirdparty)
   4. Libraries which are supplied by Duraspace projects need to be added to the Duraspace Maven repository (under releases)
   5. The Duraspace Maven repository public groups need to be revised to NOT mirror maven-central or other public repositories
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'
4. Unit/system/integration tests used to fall under 'fedora.test'
   1. now that they have been split across subprojects ('server', 'client', 'integrationtest'), they are not aggregated with a single call (i.e. fedora.test.AllUnitTests)
   2. a fix to this issue would only be needed as long as we continue to use ANT, Maven2 has its own test aggregation
5. Build number & timestamp needed for artifact names and manifest files
   • client.jar
     • needs 'fedora.version' in filename and manifest
     • needs 'build.tstamp' in manifest
   • 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://mojo.codehaus.org/buildnumber-maven-plugin/index.html
   • The build number plug-in fails if the SCM is unavailable or is not installed on the host platform. A <revisionOnScmFailure> parameter has been added to set a default build number. A warning is still shown during build but the build runs properly to completion. The default build number has been set to the "version" of the fedora-repository pom assuming that pom's version will eventually match a current or planned release.
6. 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.
7. fedora.test.integration.cma.SimpleDeploymentTests has a bug. See source file for details.
8. In creating fedorahome.zip, deploy and undeploy *.wsdd files are token-swapped (e.g. 'Fedora-API-M-Port-SOAPHTTP' to 'management').
   • This mangles token instances such as 'Fedora-API-M-Port-SOAPHTTP S'. This is a pre-existing bug.
9. Script needs to be written to support Maven Bamboo CI build
10. The file server/src/main/resources/properties/lib.properties may be a candidate for removal as it was tied to the Ant build
11. Libraries listed in server/src/resource/properties/install.properties do not automatically update with library updates and duplicate information in the pom which does not benefit from pom dependency checking
    1. Updated to be consistent with Maven dependencies but still requires manual editing
12. Split client into four modules in a branch (See Item 3 Above). Keep them under a client subdirectory.
    1. Swing Client
    2. FedoraClient Jar
    3. Messaging Client
    4. WebAdmin Client
13. Experiment with saxon, fop and imagemanip stored under a localservices directory but being dependencies of fedora-repository. This may help Eclipse since each local service is a standalone, deployable war.

...