[
http://jira.codehaus.org/browse/MJAVACC-37?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_118786
]
bentmann edited comment on MJAVACC-37 at 1/4/08 4:48 PM:
------------------------------------------------------------------
Now that all Maven-Deps have been bumped to 2.0.8, does the plugin still run
with older Maven versions? Remember, some users may still stick to Maven 2.0.x
< 2.0.8 to avoid problems with potential build breakers.
If the plugin intentionally only supports Maven >= 2.0.8, should the POM not
contain something like{code:xml}
<prerequisites>
<maven>2.0.8</maven>
</prerequisites>
{code}I'm lacking exact knowledge here, so I'm not sure whether this element is
really required and what all its side effects are.
was (Author: bentmann):
Now that all Maven-Deps have been bumped to 2.0.8, does the plugin still
run with older Maven versions? Remember, some users may still stick to Maven
2.0.x < 2.0.8 to avoid problems with potential build breakers.
If the plugin intentionally only supports Maven >= 2.0.8, should the POM not
contain something like{code:xml}
<prerequisites>
<maven>2.0.8</maven>
</prerequisites>
{code}I'm lacking exact knowledge here.
> Add mojo for running jjdoc
> --------------------------
>
> Key: MJAVACC-37
> URL: http://jira.codehaus.org/browse/MJAVACC-37
> Project: Maven 2.x JavaCC Plugin
> Issue Type: New Feature
> Affects Versions: 2.2
> Reporter: Paul Gier
> Assignee: Paul Gier
> Fix For: 2.3
>
> Time Spent: 1 day, 4 hours
> Remaining Estimate: 0 minutes
>
> A new mojo should be created that can call jjdoc.
--
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
