geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paul McMahan" <paulmcma...@gmail.com>
Subject Re: versions in artifact ids (was: Re: svn commit: r483121 - in /geronimo/server/trunk: configs/client-system/pom.xml configs/jee-specs/pom.xml modules/ge-activemq-rar/pom.xml modules/geronimo-management/pom.xml modules/geronimo-tomcat/pom.xml pom.xm
Date Wed, 06 Dec 2006 18:55:18 GMT
I agree.  This practice has the feel of a shortcut around maven's
versioning system that we may regret taking later.

Best wishes,
Paul


On 12/6/06, Jason Dillon <jason@planet57.com> wrote:
> <opinion>
> I think it is really loopy that we have version information in
> artifact ids.  A few people outside of the group have mentioned this
> too me too.
>
> IMO it would be better if the artifact ids of the specs did not have
> any version muck, and the version of that module was based on the
> spec version + a revision number.
>
> So for example, the spec here would be:
>
> <groupId>org.apache.geronimo.specs</groupId>
> <artifactId>geronimo-j2ee-management</artifactId>
> <version>1.1-1</version>
>
> (or 1.1-1-SNAPSHOT for evil mvn snapshot muck)
>
> Anyways, I'm not going to do anything about this... but I will
> continue to point out that putting version information into
> artifactIds is a poor idea... and generally a bad one at that.
> </opinion>
>
> --jason

Mime
View raw message