[MRM-1149] White/Blacklist pattern matching doesn't work for Maven-1-repos

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Won't Fix
• Affects Version/s: 1.2-M1
• Fix Version/s: Backlog
• Component/s: remote proxy
• Labels: TOMARKWONTFIX?
• Assignee: Unassigned
• Reporter: Lars Beuster
• Created: 20/Mar/09 10:43
• Updated: 15/Mar/16 06:24
• Resolved: 15/Mar/16 06:24

Description

I have a proxy connector to a Maven-1 repo.
I have a whitelist entry "my/group/**".

If I try to download an artifact with the groupId "my.group.id" then my repository is ignored.

This is because for Maven-2 repos the resolved filename is something like "my/group/id/<artifactId>".
But I have a Maven-1 repo and here the resolved filename is "my.group.id/<artifactId>".

Changing the whitelist entry to "my.group.**" still doesn't work, because the method DefaultRepositoryProxyConnector.matchesPattern() uses org.codehaus.plexus.util.SelectorUtils.matchPath() to check if the file matches a whitelist entry.
But SelectorUtils works only with the "file.separator" ("/" on Unix) to split the filename. So I have no chance of using stars in the whitelist.

As a hack I could specify the complete groupId with stars (I cannot omit the stars) "my.group.id/*" - this works. But I can't add "my.group.*" to the whitelist.

Regards
Lars

Issue Links

• is duplicated by: MRM-1035 Remote, legacy (Maven 1) repositories appear to be consulted for all artifacts, even if no appropriate proxy connector has been defined.
• is related to: MRM-1190 More fine-grained blacklist/whitelist for artifacts
• relates to: MRM-1347 Migrate repository proxy to the new repository API