I think maven needs to fix this problem in general... I was thinking
about suggesting they add dependencyGroups to dependencies, which can
be used to share config between dependencies:
<dependencyManagement>
<dependencyGroups>
<dependencyGroup>
<groupId>org.apache.openejb</groupId>
<version>2.2-incubating-SNAPSHOT</version>
<dependencies>
<dependency>
<artifactId>openejb-core</artifactId>
</dependency>
<dependency>
<artifactId>openejb-builder</artifactId>
</dependency>
<dependency>
<artifactId>openejb-pkgen-builder</artifactId>
</dependency>
<dependency>
<artifactId>openejb-yoko</artifactId>
</dependency>
<dependency>
<artifactId>openejb-sunorb</artifactId>
</dependency>
</dependencies>
</dependencyGroups>
</dependencyGroups>
</dependencyManagement>
Dunno about the exact syntax, but the general idea is to allow more
config to be shared between deps.
--jason
On Oct 4, 2006, at 11:38 AM, Dain Sundstrom wrote:
> On Oct 4, 2006, at 11:13 AM, Jason Dillon wrote:
>
>> I have been trying to remove the need for all of those
>> properties. I think a few of these are fine... just as long as
>> those properties are never used in child modules. But most people
>> copy past the deps, so these properties are bound to leak.
>
> I agree but the alternative is some pretty ugly perl code to find
> the correct version numbers to change.
>
> -dain
|