Brett,
Yesterday, this fragment in a maven.xml was working under RC3:
<ant:tar basedir="${dmc.dist.assembly.dir}"
destfile="${maven.build.dir}/${pom.id}-${env.name}- ${pom.currentVersion}.tgz"
compression="gzip" />
Today, I downloaded RC4 and observed the behaviour described.
I don't think it's a case of stale plugins in my RC3 because I always rename my ~/.maven directory before running a new release.
The maven.xml did have a stray 'xmlns:deploy="deploy"' attribute in the project tag, but it was otherwise unused. Hasn't the 'deploy' plugin gone the way of the dodo?
Steve Coy
On 29/06/2004, at 1:20 PM, Brett Porter wrote:
Steve,
I think you are mistaken: ${pom.id} has been groupId:artifactId:type since the early betas. How did this show itself?
- Brett
On Tue, 29 Jun 2004 12:03:19 +1000, Stephen Coy <[EMAIL PROTECTED]> wrote:
Hi,
I've noticed that the value of ${pom.id} has changed between RC3 and RC4.
Previously, it just returned the content of the project's <id></id> tag, but now it returns some kind of id path separated by colons "parent_id:local_id" in a multiproject environment.
It's easily fixed by replacing id with artifactId, but it did slow me down for a bit.
Steve Coy
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
