avalon framework build bug

[Stephen McConnell <mc...@apache.org>]

The avalon framework (4.1.5-dev) build has a functional bug. Using the 
current framework/maven scripts, the seperation between api and 
implementation is included in the version element of the generated resource:

    avalon-framework-4.1.5-dev-api.jar
    avalon-framework-4.1.5-dev-impl.jar

This causes a problem in Maven because the two files reference the same 
logical resource (avalon-framework).  As a result only one of the jar 
files will be introduced in the mavan build classpath.  The solution is 
to update the naming convention to correctly reflect the distinct 
resource, e.g.:

   avalon-framework-api-4.1.5-dev.jar
   avalon-framework-impl-4.1.5-dev.jar

Maven dependencies for projects dependent on the above would declare 
dependencies as follows:

    <dependency>
      <groupId>avalon-framework</groupId>
      <artifactId>avalon-framework-api</artifactId>
      <version>4.1.5-dev</version>
    </dependency>

    <dependency>
      <groupId>avalon-framework</groupId>
      <artifactId>avalon-framework-impl</artifactId>
      <version>4.1.5-dev</version>
    </dependency>

Cheers, Steve.

-- 

Stephen J. McConnell
mailto:mcconnell@apache.org
http://www.osm.net

Sent via James running under Merlin as an NT service.
http://avalon.apache.org/sandbox/merlin




---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org