Archiva

If path has leading slash when being checked againts whitelists and blacklists causes matching failure

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Cannot Reproduce
  • Affects Version/s: 1.1, 1.1.1
  • Fix Version/s: 1.1.2
  • Component/s: None
  • Labels:
    None
  • Number of attachments :
    0

Description

If path has leading slash when being checked againts whitelists and blacklists causes matching failure in DefaultRepositoryProxyConnectors::matchesPattern

eg /log4j/log4j/maven-metadata.xml and pattern "*/" will not match.

The leading slash should be removed before a comparison is made.

Issue Links

This issue relates to:
MRM-1005 Certain remote Maven2 artifacts require special leading slash in whitelist filter Major Closed
This issue is related to:
MRM-1005 Certain remote Maven2 artifacts require special leading slash in whitelist filter Major Closed

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
James William Dumay added a comment -

Seems I could not reproduce this bug in later revisions of trunk.

Show
James William Dumay added a comment - Seems I could not reproduce this bug in later revisions of trunk.
Hide
Permalink
b v j added a comment -

MRM-1005 expands on the bug described here

Show
b v j added a comment - MRM-1005 expands on the bug described here

People

Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved:
Atlassian JIRA (v4.4.3#663-r165197) | Report a problem
Powered by a free Atlassian JIRA open source license for Codehaus. Try JIRA - bug tracking software for your team.