You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org> on 2009/12/29 21:46:55 UTC
[jira] Closed: (MSHADE-68) Artifact filter misbehaves when plugin
run on Windows
[ http://jira.codehaus.org/browse/MSHADE-68?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benjamin Bentmann closed MSHADE-68.
-----------------------------------
Resolution: Fixed
Fix Version/s: 1.3
Assignee: Benjamin Bentmann
Fixed in [r894479|http://svn.apache.org/viewvc?view=revision&revision=894479].
> Artifact filter misbehaves when plugin run on Windows
> -----------------------------------------------------
>
> Key: MSHADE-68
> URL: http://jira.codehaus.org/browse/MSHADE-68
> Project: Maven 2.x Shade Plugin
> Issue Type: Bug
> Affects Versions: 1.2.2
> Environment: Windows
> Reporter: Benjamin Bentmann
> Assignee: Benjamin Bentmann
> Fix For: 1.3
>
>
> Consider a configuration like
> {code:xml}
> <configuration>
> <filters>
> <filter>
> <artifact>foo:bar</artifact>
> <includes>
> <include>**/a.properties</include>
> </includes>
> <excludes>
> <exclude>org/apache/*</exclude>
> </excludes>
> </filter>
> </filters>
> </configuration>
> {code}
> When the plugin gets executed on Windows, this will erroneously exclude the path "a.properties" (though included by "\*\*/a.properties") and "org/apache/maven/a.properties" (though not excluded by "org/apache/\*").
> This is due to misuse of util methods that expect the platform-specific file separator to be used for the paths but the plugin uses the unaltered strings from its configuration. This discrepancy prevents proper directory splitting, leading to the described mismatches.
--
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