Commons Parent 22 is now in Maven Central.

Components that upgrade to this release should note the following:

Starting with version 22, the RAT plugin has changed Maven group and
id, so any existing configuration needs to be updated.

    To fix component POMs, please change any occurrences of:
        <groupId>org.codehaus.mojo</groupId>
        <artifactId>rat-maven-plugin</artifactId>
    to the new values:
        <groupId>org.apache.rat</groupId>
        <artifactId>apache-rat-plugin</artifactId>

Version 22 has fixed the resources and testResources settings; if the
component pom includes definitions of these they should be reviewed to
see if they are still necessary. CP 22 has the following definitions:

    <resources>
      <!-- This is the default setting from the super-pom -->
      <resource>
        <directory>src/main/resources</directory>
      </resource>
      <!-- hack to ensure the N&L appear in jars -->
      <resource>
        <directory>${basedir}</directory>
        <targetPath>META-INF</targetPath>
        <includes>
          <include>NOTICE.txt</include>
          <include>LICENSE.txt</include>
        </includes>
      </resource>
    </resources>

    <!-- ensure test jars also get NOTICE & LICENSE files -->
    <testResources>
      <!-- This is the default setting from the super-pom -->
      <testResource>
        <directory>src/test/resources</directory>
      </testResource>
      <!-- hack to ensure the N&L appear in jars -->
      <testResource>
        <directory>${basedir}</directory>
        <targetPath>META-INF</targetPath>
        <includes>
          <include>NOTICE.txt</include>
          <include>LICENSE.txt</include>
        </includes>
      </testResource>
    </testResources>

If the component uses the standard Maven directory layout, there
should be no need for its pom to redefine either resources or
testResources.

The site plugin has been updated to version 3.0 to allow use with Maven 3.

The plugin has changed behaviour [1].
The command "mvn site:stage-deploy" no longer builds the site for you,
you have to use "mvn site:site" first; similarly for "mvn
site:deploy".

Also "mvn site" changes the order of entries under "Project Reports";
these used to be alphabetic by report name. Don't know yet whether
there is a solution.

Note: it took 5 hours or so from Nexus release to arrival in Central

[1] 
http://maven.apache.org/plugins/maven-site-plugin/migrate.html#From_2.2.x_to_2.3.x

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Reply via email to