[
http://jira.codehaus.org/browse/MJAVACC-27?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paul Gier updated MJAVACC-27:
-----------------------------
Attachment: MJAVACC-27-javacc-maven-plugin-r5255.patch
I like the idea in this issue. I'm attaching a slightly modified patch, that
adds the same feature to the jjtree mojo. Also I changed the behaviour
slightly so that the package name parameter takes precedence over the one in
the jj file. That way you don't have to fail if the two names do not match.
> Multiple grammar issue
> ----------------------
>
> Key: MJAVACC-27
> URL: http://jira.codehaus.org/browse/MJAVACC-27
> Project: Maven 2.x JavaCC Plugin
> Issue Type: Bug
> Reporter: Stefano Fornari
> Attachments: JavaCCMojo.java,
> MJAVACC-27-javacc-maven-plugin-r5255.patch, multi-grammar-2.patch
>
>
> Hi All,
> I have multiple grammar files, each going into a different package.
> Therefore, I cannot specify either the output directory nor the
> package. I created the attached pom, but when maven generates the
> parser, all source codes go in the same generated-files directory.
> Looking at the code of the plug-in, it looks like it is a limitation
> in the plug-in (please forgive me if I am saying an heresy, it is the
> first time I see a mojo... :) ).
> Therefore, I would like to propose a little change: the grammar is searched
> for a package declaration, if it is found it is used like if it was specified
> as plugin property. I would aslo skeep processing ig the output directory
> does not exist. This helps in specifying the plug-in in a parent project even
> if any of the subprojects does not have javacc grammars.
> Please see the attached pacth and class.
--
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
