JIRA please ;-)
did you test it with a snapshot of 2.0.2?
-D
On 1/5/06, Chris Berry <[EMAIL PROTECTED]> wrote:
>
> We have seen the same issue, and it is a serious PITA.
> Now we will have to go through any home grown Plugins and modify them
> accordingly.
>
> 1) the absolute path makes more sense, and more importantly, matches all
> previous behavior, particularly m1!!
> 2) this sort of change should come with a huge red flag attached, as it
> breaks peoples code. It certainly shouldn't come in a minor release
>
> Thus, I can only assume that this is an bug??
> Can we expect this to be fixed in 2.0.2??
> Thanks,
> -- Chris
>
>
> On 1/5/06, Jens Zastrow <[EMAIL PROTECTED]> 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]
> >
> >
>
>
