[ http://jira.codehaus.org/browse/MOJO-215?page=all ]
Jesse McConnell closed MOJO-215:
--------------------------------
Resolution: Won't Fix
the underlying issue here is that your pom is redefining the outputDirectory
and when that is picked up by the eclipse plugin the wrong source reference is
placed in the .classpath file.
instead of redefining the output directory to include the package name, use the
packageName configuration option to set the appropriate packageName, it will be
appended to the end of the outputDirectory when the javacc process is called.
> JavaCC and the Eclipse plugin conflict when generated sources are in packages
> -----------------------------------------------------------------------------
>
> Key: MOJO-215
> URL: http://jira.codehaus.org/browse/MOJO-215
> Project: Mojo
> Type: Bug
> Components: javacc
> 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
