Hello,
I just upgraded to Maven 1.0 RC3 and found that the variable
maven.dependency.classpath is null when I try to use it in my custom
goals (which have all broken as a result of this).
I have the following goal:
<goal name="echoClassPath">
<ant:echo>
CP is ${context.getVariable('maven.dependency.classpath')}
</ant:echo>
</goal>
When I run it, I get:
echoClassPath:
[echo] CP is:
BUILD SUCCESSFUL
Total time: 5 seconds
What is going on here? I've tried referring to the variable as
${maven.dependency.classpath} as well, no luck.
If I run Maven with -X, I see...
[DEBUG] Adding reference: maven.dependency.classpath ->
/home/gbauman/.maven/repository/mysql/jars/mysql-connector-java-3.0.11-stable-bin.jar
[DEBUG] Adding reference: maven-classpath ->
[DEBUG] Adding reference: maven.compile.src.set ->
Processing dependencies for project middleware; classloader
[ForeheadClassLoader: name="root.maven"]
adding dependency
/home/gbauman/.maven/repository/mysql/jars/mysql-connector-java-3.0.11-stable-bin.jar
into project classloader
... so I *know* maven sees the dependency and thinks it is filling the
variable.
Can anyone shed any light on this?
--
Gabriel Bauman <[EMAIL PROTECTED]>
Bravenet Web Services Inc.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
