maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dennis Lundberg (JIRA)" <j...@codehaus.org>
Subject [jira] Commented: (MRESOURCES-52) Change type of plugin parameter "outputDirectory" to java.io.File
Date Mon, 14 Jan 2008 21:40:59 GMT

    [ http://jira.codehaus.org/browse/MRESOURCES-52?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_119879
] 

Dennis Lundberg commented on MRESOURCES-52:
-------------------------------------------

Will this affect users of the plugin, with regards to the way they configure it?
If so then we need some documentation for this in the plugin site:
"In version -2.2 it worked this way, but in version 2.3+ it works like this..."

> 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

        

Mime
View raw message