[
http://jira.codehaus.org/browse/MJAVACC-87?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=149434#action_149434
]
Benjamin Bentmann commented on MJAVACC-87:
------------------------------------------
For the record: There seems to be an issue with IDEA's Maven integration
([IDEA-19177|http://www.jetbrains.net/jira/browse/IDEA-19177]) that causes the
interim output of JJTree/JTB to be registered as a compile source root although
the JavaCC Plugin does not actually declare it as such. This causes duplicate
class errors...
> Allow customized parser sources to reside in src/main/java
> ----------------------------------------------------------
>
> Key: MJAVACC-87
> URL: http://jira.codehaus.org/browse/MJAVACC-87
> Project: Maven 2.x JavaCC Plugin
> Issue Type: Improvement
> Components: javacc, jjtree, jtb
> Affects Versions: 2.4
> Reporter: Benjamin Bentmann
> Assignee: Benjamin Bentmann
> Fix For: 2.5
>
>
> The plugin currently requires users to place custom source files next to the
> grammar file as explained in the
> [FAQ|http://mojo.codehaus.org/javacc-maven-plugin/faq.html]. As Jason Dillon
> pointed out on the mail thread [JavaCC Maven Plugin at
> Geronimo|http://www.nabble.com/Re%3A-JavaCC-Maven-Plugin-at-Geronimo-p17786080.html],
> this is odd and I agree. Why should custom Java sources for the parser not
> live next to all the other Java sources in {{src/main/java}}?
--
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
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
