Re: Release of Commons POM?

[Phil Steitz]

On 10/6/06, Jochen Wiedmann <[EMAIL PROTECTED]> wrote:

Hi,

as already discussed in

    http://marc.theaimsgroup.com/?t=115719054100004

I would like to approach a release of the commons POM.

- At the time of the above thread, the maven-changes-plugin was available as a
  snapshot release only. In the meantime, this has changed.
- The POM is using a resource with the base directory as resource
  directory. As discussed, this is causing problems with the
maven-source-plugin.
  Therefore, I propose to replace
      <resources>
        <resource>
          <directory>${basedir}</directory>
          <includes>
            <include>NOTICE.txt</include>
            <include>LICENSE.txt</include>
          </includes>
          <targetPath>META-INF</targetPath>
        </resource>
      </resources>
  with
      <plugin>
                <!-- This should possibly better be done by using a resource
                     definition. However, if we declare a resource with
                     ${basedir} as the base directory, then the
                     maven-source-plugin will add the whole directory to
                     its contents.
                -->
        <artifactId>maven-antrun-plugin</artifactId>
        <executions>
          <execution>
            <phase>generate-resources</phase>
            <configuration>
              <tasks>
                <copy todir="${project.build.outputDirectory}/META-INF">
                  <fileset dir="${basedir}">
                    <include name="LICENSE.txt"/>
                    <include name="NOTICE.txt"/>
                  </fileset>
                </copy>
              </tasks>
            </configuration>
            <goals>
              <goal>run</goal>
            </goals>
          </execution>
        </executions>
      </plugin>

+1

There is one additional issue, which I do have myself. Checking out
the trunks-proper directory  in order to edit the POM will typically
result in checking out all of jakarta-commons. Obviously, that's not
what I want. Therefore, I propose to create a module
commons/commons-parent, change the pom's artifactId from "commons" to
"commons-parent" and move the POM to that place.

+1

Once that is decided (and possibly done): Are there any further issues
or are we ready for a vote?

I would also like to find a way to decouple the inherited site
elements from the parent POM.  The current setup will publish the
parent site metadata with the POM, so site l & f changes will require
re-release of the POM, which I don't like.  Is there any way to
accomplish this other than to create commons-site and then all the
foo-sites separately?

Thanks for pushing this along.

Phil

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]