maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benjamin Bentmann (JIRA)" <>
Subject [jira] Closed: (MCLEAN-31) Always resolve relative path against the project's base directory
Date Wed, 03 Sep 2008 21:38:48 GMT


Benjamin Bentmann closed MCLEAN-31.

         Assignee: Benjamin Bentmann
       Resolution: Fixed
    Fix Version/s: 2.3

Fixed in [r691788|].

> Always resolve relative path against the project's base directory
> -----------------------------------------------------------------
>                 Key: MCLEAN-31
>                 URL:
>             Project: Maven 2.x Clean Plugin
>          Issue Type: Bug
>    Affects Versions: 2.2
>            Reporter: Benjamin Bentmann
>            Assignee: Benjamin Bentmann
>             Fix For: 2.3
>         Attachments:, 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:
For more information on JIRA, see:


View raw message