[
http://jira.codehaus.org/browse/MJAVACC-57?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_121837
]
Paul Gier commented on MJAVACC-57:
----------------------------------
Instead of having a new mojo for this and then deprecating the current jjtree
mojo, you can probably just replace the current jjtree mojo with this new one.
Even though it will break some builds, if we make this a 3.0 version and have
the relevant documentation on the site, I think it will be ok. Maybe there can
just be a flag to skip the javacc compilation and use the output directory
instead of the interim directory for users that want to temporarily stick with
the old setup.
As far as the timestamp stuff, as long as it works in the normal use cases I
say go for it.
> Allow jjtree to automatically execute javacc
> --------------------------------------------
>
> Key: MJAVACC-57
> URL: http://jira.codehaus.org/browse/MJAVACC-57
> Project: Maven 2.x JavaCC Plugin
> Issue Type: New Feature
> Components: jjtree
> Reporter: Paul Gier
> Assignee: Benjamin Bentmann
> Fix For: 2.x
>
>
> The common use case for jjtree is to first run the jjtree-mojo and then run
> the javacc-mojo on the output of jjtree. This requires the configuration of
> two mojo executions. It would be nice if the jjtree mojo automatically
> called javacc on it's output by default. This way only one execution would
> be needed.
--
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
