You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "John Casey (JIRA)" <ji...@codehaus.org> on 2010/09/10 22:57:32 UTC
[jira] Created: (MSHARED-162) actTransitively wildcard patterns can
fail on pattern-based filters
actTransitively wildcard patterns can fail on pattern-based filters
-------------------------------------------------------------------
Key: MSHARED-162
URL: http://jira.codehaus.org/browse/MSHARED-162
Project: Maven Shared Components
Issue Type: Bug
Components: maven-common-artifact-filters
Affects Versions: maven-common-artifact-filters 1.2
Reporter: John Casey
When a pattern is matched against the dependency trail of an artifact in the PatternInclusionArtifactFilter and PatternExclusionArtifactFilter, the whole trail is considered at once (using a comma-separated list of items in the trail). This means that only particular wildcard patterns will ever match, and it should be virtually impossible to use an exact match.
A far better approach would be to iterate through the dependency trail and try to match the patterns against each dep-trail item separately, to avoid problems of detecting the boundaries between items during the pattern-matching process.
--
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
[jira] Closed: (MSHARED-162) actTransitively wildcard patterns can
fail on pattern-based filters
Posted by "John Casey (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MSHARED-162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
John Casey closed MSHARED-162.
------------------------------
Resolution: Fixed
Fix Version/s: (was: maven-common-artifact-filters 1.4)
maven-common-artifact-filters 1.3
> actTransitively wildcard patterns can fail on pattern-based filters
> -------------------------------------------------------------------
>
> Key: MSHARED-162
> URL: http://jira.codehaus.org/browse/MSHARED-162
> Project: Maven Shared Components
> Issue Type: Bug
> Components: maven-common-artifact-filters
> Affects Versions: maven-common-artifact-filters 1.2
> Reporter: John Casey
> Assignee: John Casey
> Fix For: maven-common-artifact-filters 1.3
>
>
> When a pattern is matched against the dependency trail of an artifact in the PatternInclusionArtifactFilter and PatternExclusionArtifactFilter, the whole trail is considered at once (using a comma-separated list of items in the trail). This means that only particular wildcard patterns will ever match, and it should be virtually impossible to use an exact match.
> A far better approach would be to iterate through the dependency trail and try to match the patterns against each dep-trail item separately, to avoid problems of detecting the boundaries between items during the pattern-matching process.
--
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
[jira] Updated: (MSHARED-162) actTransitively wildcard patterns can
fail on pattern-based filters
Posted by "John Casey (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MSHARED-162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
John Casey updated MSHARED-162:
-------------------------------
Fix Version/s: maven-common-artifact-filters 1.3
> actTransitively wildcard patterns can fail on pattern-based filters
> -------------------------------------------------------------------
>
> Key: MSHARED-162
> URL: http://jira.codehaus.org/browse/MSHARED-162
> Project: Maven Shared Components
> Issue Type: Bug
> Components: maven-common-artifact-filters
> Affects Versions: maven-common-artifact-filters 1.2
> Reporter: John Casey
> Assignee: John Casey
> Fix For: maven-common-artifact-filters 1.3
>
>
> When a pattern is matched against the dependency trail of an artifact in the PatternInclusionArtifactFilter and PatternExclusionArtifactFilter, the whole trail is considered at once (using a comma-separated list of items in the trail). This means that only particular wildcard patterns will ever match, and it should be virtually impossible to use an exact match.
> A far better approach would be to iterate through the dependency trail and try to match the patterns against each dep-trail item separately, to avoid problems of detecting the boundaries between items during the pattern-matching process.
--
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
[jira] Updated: (MSHARED-162) actTransitively wildcard patterns can
fail on pattern-based filters
Posted by "John Casey (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MSHARED-162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
John Casey updated MSHARED-162:
-------------------------------
Fix Version/s: (was: maven-common-artifact-filters 1.3)
maven-common-artifact-filters 1.4
> actTransitively wildcard patterns can fail on pattern-based filters
> -------------------------------------------------------------------
>
> Key: MSHARED-162
> URL: http://jira.codehaus.org/browse/MSHARED-162
> Project: Maven Shared Components
> Issue Type: Bug
> Components: maven-common-artifact-filters
> Affects Versions: maven-common-artifact-filters 1.2
> Reporter: John Casey
> Assignee: John Casey
> Fix For: maven-common-artifact-filters 1.3
>
>
> When a pattern is matched against the dependency trail of an artifact in the PatternInclusionArtifactFilter and PatternExclusionArtifactFilter, the whole trail is considered at once (using a comma-separated list of items in the trail). This means that only particular wildcard patterns will ever match, and it should be virtually impossible to use an exact match.
> A far better approach would be to iterate through the dependency trail and try to match the patterns against each dep-trail item separately, to avoid problems of detecting the boundaries between items during the pattern-matching process.
--
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