[
http://jira.codehaus.org/browse/MCLEAN-31?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=146733#action_146733
]
Will Horn commented on MCLEAN-31:
---------------------------------
Is there a reason why absolute paths are not addressed? In my case, I need to
delete a directory with absolute path stored in a custom ${} parameter. The
build creates the directory and clean should remove it.
I've found that "mvn clean" works when I am in the project dir, but due to the
MCLEAN-27 fix, it fails when run from a parent dir.
> Always resolve relative path against the project's base directory
> -----------------------------------------------------------------
>
> Key: MCLEAN-31
> URL: http://jira.codehaus.org/browse/MCLEAN-31
> Project: Maven 2.x Clean Plugin
> Issue Type: Bug
> Affects Versions: 2.2
> Reporter: Benjamin Bentmann
> Attachments: clean.zip, relative-paths.patch, relative-paths.patch
>
>
> Relative paths - which are often used by users for plugin configuration in
> the POM - must always be resolved against the base directory of the current
> project. By always I mean not just when run in a reactor build.
> Attached is a patch to fix the mojo as well as a mini project to reveal the
> bug. Just unpack the project, change your working directory to the parent
> folder of its base directory or any other directory that does not contain the
> POM and run Maven on the test POM from this working directory using its -f
> switch. The plugin will not delete the "test-target" directory in the project
> base directory but instead delete an equally named directory in the current
> working directory.
--
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
