[
https://jira.codehaus.org/browse/MASSEMBLY-607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kristian Rosenvold updated MASSEMBLY-607:
-----------------------------------------
Fix Version/s: (was: 2.5.2)
> Wildcard in dependencySet/includes doesn't match artifact with empty
> classifier
> -------------------------------------------------------------------------------
>
> Key: MASSEMBLY-607
> URL: https://jira.codehaus.org/browse/MASSEMBLY-607
> Project: Maven Assembly Plugin
> Issue Type: Bug
> Components: dependencySet
> Affects Versions: 2.3
> Environment: Windows 7/Maven 3.0.03
> Reporter: Alexander Kormushin
>
> Following dependency set will match only my jar artifacts with any non-empty
> classifier:
> {code}
> <dependencySet>
> <includes>
> <include>com.mycompany.*:*:jar:*:*</include>
> </includes>
> </dependencySet>
> {code}
> But it seems wildcard should include empty ones.
> Here is the related code fragment:
> {code:title=.m2\repository\org\apache\maven\shared\maven-common-artifact-filters\1.4\maven-common-artifact-filters-1.4.jar!\org\apache\maven\shared\artifact\filter\PatternIncludesArtifactFilter.class}
> 172 private boolean matchAgainst( final String value, final List patterns,
> final boolean regionMatch )
> 181 // fail immediately if pattern tokens outnumber tokens to match
> 182 boolean matched = ( patternTokens.length <= tokens.length );
> {code}
> I have following values achieving 182 line:
> pattern=[com.mycompany.*, *, jar, *, *]
> tokens=[com.mycompany, myproject, jar, 1.0.0-SNAPSHOT]
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
