Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Testing
  • Upgrade components reporting plugins to use the latest versions (doing this first means any problems with plugins can be identified and fixed first - otherwise the cause might be either the plugin or Maven 3)
  • Update commons-parent
    • Add reporting plugins to <dependencyManagement> section
    • Site Plugin configuration - either:
      • remove <reporting> section and configure maven-site-plugin in the main <build> section
      • add a Maven 3 profile (automatically activated when M3 is used) with the site plugin configured - see example here
    • Release commons-parent
    • Release commons-sandbox-parent
  • Update component pom's (if commons decides to adopt M3 support)
    • Update to use new commons-parent release
    • Site Plugin configuration - either:
      • remove <reporting> section and configure maven-site-plugin in the main <build> section
      • add a Maven 3 profile (automatically activated when M3 is used) with the site plugin configured - see example here

Testing

Test

Comment

Completed

mvn -Prc clean package

Run for all proper components - need to test Sandbox components

2010-10-06

mvn -Prc clean install

Current problem with gpg plugin

 

mvn site

Requires config update and plugin upgrades

 

mvn -Ptest-deploy site

 

 

release plugin

 

 

Nexus Release

 

 

mvn commons:download-page

 

2010-10-06

mvn commons:mail-page

 

2010-10-06

mvn commons:jira-page

 

2010-10-06

mvn commons:sandbox-jira-page

 

 

commons-build-plugin build

currently not building

 

mvn -Pjava-1.3 test

uses different surefire-plugin version

 

mvn -Pjava-1.4 test

 

 

mvn -Pjava-1.5 test

 

 

mvn -Pjava-1.6 test

 

 

Commons Site

 

 

mvn -Ptrunks-proper clean package

 

 

mvn -Ptrunks-sandbox clean package

 

 

mvn -Pci ???