activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Fritz Oconer" <foco...@exist.com>
Subject Re: ActiveMQ POM
Date Tue, 14 Nov 2006 16:41:43 GMT
Hi,

I added ${activemq-version} instead of ${project.version} basically as a 
workaround for build failures due to differences in timestamp. If we use 
${project.version} then it will require all activemq type artifacts 
(specified as <dependency> in the parent pom.xml) to have the same timestamp 
as the parent. This becomes an issue when nightly-build deploy fails after 
some of the modules have been deployed causing some activemq modules to have 
different timestamp as the parent. We can change this back to using 
project.version but we need to make sure that nightly-build always deploys 
successfully or I wonder if there is another workaround for this?

https://issues.apache.org/activemq/browse/AMQ-956

Regards,
Fritz

----- Original Message ----- 
From: "Hiram Chirino" <hiram@hiramchirino.com>
To: <activemq-dev@geronimo.apache.org>
Sent: Tuesday, November 14, 2006 8:48 PM
Subject: ActiveMQ POM


> Howdy,
>
> I was wondering if anybody knows why we are using
> "${activemq-version}" instead of "${project.version}" in our ActiveMQ
> poms??  When doing a release build, it's easy to forget that you need
> to updated the version in to places.  Can't we just use the
> "${project.version}" variable??
>
> -- 
> Regards,
> Hiram
>
> Blog: http://hiramchirino.com 


Mime
View raw message