[
http://jira.codehaus.org/browse/MRESOURCES-52?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann updated MRESOURCES-52:
----------------------------------------
Attachment: resources.zip
Attached is now a mini project for you to experience this bug yourself. Just
extract the archive. Then call Maven from a working directory that is not equal
to the base directory of the project, e.g. issue "cd .." and then "mvn -f
resources/pom.xml". You will notice that the resources get placed into the
current working directory instead of the project's base directory.
> Change type of plugin parameter "outputDirectory" to java.io.File
> -----------------------------------------------------------------
>
> Key: MRESOURCES-52
> URL: http://jira.codehaus.org/browse/MRESOURCES-52
> Project: Maven 2.x Resources Plugin
> Issue Type: Bug
> Affects Versions: 2.2
> Reporter: Benjamin Bentmann
> Assignee: Milos Kleint
> Fix For: 2.3
>
> Attachments: output-directory.patch, resources.zip
>
>
> As described by MNG-3273, using java.lang.String for path parameters is
> discouraged as it usually leads to relative paths being resolved against the
> current working directory instead of the project's base directory. This bug
> manifest itselfs when a user explicitly configures the maven-resources-plugin
> with a relative output directory and then runs the build from a different
> working directory (for example, the base directory of an aggregator parent).
--
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
