Sorry, for those who don't have it, the URL for this issue is:
http://jira.codehaus.org/browse/MNG-1927
Thanks,
John
John Casey wrote:
Hi all,
Can I get some testers out there to retry this functionality using a
fresh build from:
http://svn.apache.org/repos/asf/maven/components/branches/maven-2.0.x/
It should be fixed now.
Thanks,
John
Jens Zastrow wrote:
In Maven 2.0 the value containes the whole absolute path to the target
dir.
C:\windows\system32\target
With Maven 2.0.1 only:
target\
I use the JavaCC-plugin:
<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>javacc-maven-plugin</artifactId>
<version>0.6.1-SNAPSHOT</version>
<configuration>
<outputDirectory>${project.build.directory}/generated-src/main/java</out
putDirectory>
</configuration>
....
</plugin>
The problem now arise when the project with javacc is part of a
multi-module build (with 2.0.1).
Because ${project.build.directory}/generated-src/main/java evalulates to
target/generated-src/main/java the files are generated to the
parent-project target-directory!
Which value should ${project.build.directory} contain?
Thanks
Workaround: Its simple to fix this in the pom.xml using
${basedir}/target/generated-src/main/java.
---------------------------------------------------------------------
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]
