On Mon, 29 Aug 2005, Gilles Scokart wrote:
Hi Gilles,
> I have tried to use ${project.compileClasspathElements} into the
> configuration tag of a plugin (antrun), and it seems to work.
How did you use it? Could you post the pom.xml?
> But when I use ${project.runtimeClasspathElements}, I only have the same
> result. The pure runtime dependencies are not present in the list.
That's because all compile time dependencies are also runtime
dependencies. See
http://maven.apache.org/maven2/dependency-mechanism.html#dependency_scope
> Is it a general behaviour that can be used in any plugin or is it specific
> to antrun ?
It's general behaviour.
> Where can we found the list of defined variables ?
In antrun you can use ${project.*} where * is any MavenProject.java
property (get*), but you already figured that out. Other than that,
just ${basedir} is available (and your own custom defined properties,
and those ant provides by default).
> Why is the project.runtimeClasspathElements not set correctly? Is it a bug?
> Did I made something wrong?
I'm really curious how you intend to use this.. AFAIK it'll return
something like "[/path/to/a.jar,/path/to/b.jar]".
>
> Thanks,
> Gilles Scokart
>
> _________________________________________________________________
> Cr�ez gratuitement votre espace perso en ligne avec MSN Spaces !
> http://spaces.msn.com/?mkt=fr-be
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
--
Kenney Westerhof
http://www.neonics.com
GPG public key: http://www.gods.nl/~forge/kenneyw.key
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
