[
https://issues.apache.org/jira/browse/MCLEAN-31?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17958662#comment-17958662
]
Olivier Lamy commented on MCLEAN-31:
------------------------------------
This project has moved from Jira to GitHub Issues. This issue was migrated to
[apache/maven-clean-plugin#217|https://github.com/apache/maven-clean-plugin/issues/217].
> Always resolve relative path against the project's base directory
> -----------------------------------------------------------------
>
> Key: MCLEAN-31
> URL: https://issues.apache.org/jira/browse/MCLEAN-31
> Project: Maven Clean Plugin (Moved to GitHub Issues)
> Issue Type: Bug
> Affects Versions: 2.2
> Reporter: Benjamin Bentmann
> Assignee: Benjamin Bentmann
> Priority: Major
> Fix For: 2.3
>
> 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 was sent by Atlassian Jira
(v8.20.10#820010)
