This starts to sound like you need to either use macrodef (to use different
refid names for different projects, i.e. @{project}.classpath.runtime), or
<ant inheritall="false">.
And btw, macrodef doesn't work in maven (here, at least).
--Original Message Text---
From: sporty
Date: Wed, 19 Oct 2005 16:07:10 -0600
Lemme rewrite that email. Some of it didn't make sense.
Maven2's antlib can create a reference id for me, which is a set of custom
tasks. There's a condition where I rather not use maven2's antlib but use
<path id="..">.
Here's the sniplet:
<target name="dependencyRunTimeTrue" if="project.dependency.runtime">
<artifact:dependencies verbose="true" useScope="runtime"
pathId=
"project.classpath.runtime">
<artifact:pom file="pom.xml" />
<artifact:remoteRepository
url="${project.remoteReposito
ry} " />
</artifact:dependencies>
</target>
<target name="dependencyRunTimeFalse"
unless="project.dependency.runtime
">
<path id="project.classpath.runtime"/>
</target>
If i replace artifact:.. with a regular <path id="..."> of the same name, it
works fine. Is this a bug in maven2 or ant?
On 10/19/05, sporty <[EMAIL PROTECTED]> wrote: I ran into this using antlib
w/ maven. It dynamically choses to create a path refid if I so choose to.
I'm guessing mavne2's antlib, which has custom ant tasks, doesn't jibe when
using reference ids.
On 10/19/05, Juergen Hermann <[EMAIL PROTECTED]> wrote: On Wed, 19 Oct 2005
15:34:48
-0600, sporty wrote:
^><target name="dependencyRunTimeFalse" unless="project.dependency.runtime">
><path id="project.classpath.runtime"/>
></target>
>That's when I ran into this error:
>C:\development\eclipse 3.0\workspace\hibernate-3\common.xml:7: Reference ID
>project.classpath.runtime already exists
How is project.dependency.runtime set? You should do it via a <isrefeence>
condition, and then it should work.
Ciao, Jürgen
Ciao, Jürgen
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
