commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ralph Goers <>
Subject Re: [all] Rebooting commons projects
Date Mon, 18 May 2009 07:53:28 GMT

On May 18, 2009, at 12:19 AM, Jörg Schaible wrote:
> I think we more or less all agree that such a new component should  
> play nice
> with an older version in the classpath. However, while I am all for
> evolving the current project with a new major release, we have to  
> consider
> that it is not possible to have the same artifact twice in the same  
> Maven
> project with a different version only. It does not matter if foo-1.x  
> can be
> used at same time with foo-2.x, Maven does simply not support this
> scenario. Therefore we would have to change the artifact name anyway  
> to
> something like foo2-2.x ...

For many commons projects this is easy. Many of them are using a  
groupId of commons-projectName, which typically is also the same as  
the artifactId. The "correct" groupId should be org.apache.commons so  
simply changing that would solve the problem.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message