> 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?
I will try to clean it a little bit, then I will post it here.
> 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
Yes, but runtime class path should contain more. It should contain the
compile + pure runtime dependencies.
> Is it a general behaviour that can be used in any plugin or is it
specific
> to antrun ?
It's general behaviour.
Does it mean that we can use $project.xxx in the configuration of other
plugin. Is there other variable than $project. For instance, I have tried
(unsuccessfully) to found a varaible that map to the local repository.
I'm really curious how you intend to use this.. AFAIK it'll return
something like "[/path/to/a.jar,/path/to/b.jar]".
That's exactly what I receive. I use it because I have a project that build
an ant task, and I want to test this ant task by executing it from the pom,
in the testing phase.
I use this value, to set a classpath. I use a series of echo and relplace
to format it correctly.
_________________________________________________________________
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]
