[ http://jira.codehaus.org/browse/MJAVACC-7?page=all ]
Brett Porter moved MOJO-215 to MJAVACC-7:
-----------------------------------------
Component: (was: javacc)
Key: MJAVACC-7 (was: MOJO-215)
Project: Maven 2.x Javacc Plugin (was: Mojo)
> JavaCC and the Eclipse plugin conflict when generated sources are in packages
> -----------------------------------------------------------------------------
>
> Key: MJAVACC-7
> URL: http://jira.codehaus.org/browse/MJAVACC-7
> Project: Maven 2.x Javacc Plugin
> Type: Bug
> Environment: Fedora core 4 with Maven 2.0.1, Eclipse plugin 2.0 and JavaCC
> plugin 0.5
> Reporter: Terence Haddock
> Assignee: Jesse McConnell
> Attachments: javacc.patch, javacctest.zip
>
>
> When I use the JavaCC plugin and the generated sources are in a package
> (com.tripi.test for example), the Eclipse plugin will use JavaCC's
> outputDirectory variable as the source directory. The problem is, then
> Eclipse complains that the .java files are not in the right location and will
> not recognize them, no matter what javacc's outputDirectory is set to.
> Attached is a sample project. Run "mvn eclipse:eclipse", then open the
> project in Eclipse. Although the project compiles and the tests run fine from
> "mvn test", Eclipse has real problems with this project.
> A temporary workaround for my project is to add a "sourceRoot" parameter to
> the javacc Maven plugin (patch attached), but I am not sure if this is a
> correct solution.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
