[
http://jira.codehaus.org/browse/MJAVACC-35?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_112896
]
Benjamin Bentmann commented on MJAVACC-35:
------------------------------------------
bq. Usually, relative paths need to be manually resolved against
project.getBasedir()
Hm, if I get [Guide to Developing Java Plugins: Files and
Directories|http://maven.apache.org/guides/plugin/guide-java-plugin-development.html]
correctly, this whole stuff about getAbsolutePath() would not be necessary if
the mojo parameters that take files were declared of type java.io.File instead
of String. The plexus container seems to automatically resolve relative paths
against the project base directory when configuring the mojo. That's at least
what I figured out from some other plugin that logs its unaltered parameter
which comes out as absolute despite being specified as relative in the POM.
> If input and output directory are equal then input files are emptied
> --------------------------------------------------------------------
>
> Key: MJAVACC-35
> URL: http://jira.codehaus.org/browse/MJAVACC-35
> Project: Maven 2.x JavaCC Plugin
> Issue Type: Bug
> Affects Versions: 2.3
> Environment: WinXP
> Reporter: Tim Pizey
> Attachments: JavaCCMojo.patch
>
>
> If the inputDirectory is the same as the outputDirectory, a situation which
> no doubt should not happen, but has to in javacc itself,
> then the input files are replaced with zero byte size files.
--
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
