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" <[EMAIL PROTECTED]>
To: <[email protected]>
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
