[
http://jira.codehaus.org/browse/MJAVACC-58?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_121320
]
Benjamin Bentmann commented on MJAVACC-58:
------------------------------------------
For high expressiveness, all configuration elements taking paths should be
explicitly provided in the POM as relative paths, e.g. "src/main/javacc". Just
calling the mojos using the default values that Maven derives from evaluating
expressions like {{${project.*}}} or {{${basedir}}} will usually not trigger
the bugs related to path handling as those expressions deliver absolute paths.
> Add a multi-module project to the integration tests.
> ----------------------------------------------------
>
> Key: MJAVACC-58
> URL: http://jira.codehaus.org/browse/MJAVACC-58
> Project: Maven 2.x JavaCC Plugin
> Issue Type: Improvement
> Reporter: Paul Gier
> Priority: Minor
>
> It would be good to have at least one multi-module project in the integration
> tests. This could verify that the paths work correctly when javacc or the
> other mojos are running in a module instead of in the base project.
--
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
