As Joakim noticed, my quick-fix patch breaks many testcases. It also doesn't covers some valid cases, like the use of classifiers with "-" tokens.
Still looking for a working artifactId detection strategy... I myself sometime hardly discover the artifactId. Lets look at groovy : "groovy-1.0-jsr-06" Is this "groovy" artifact with version "1.0-jsr-06", or (as it is in repo) "groovy-1.0-jsr" version "06" ? I'm not sure there is any fully deterministic way to solve this. Maybe the only way to solve this is to have RepositoryLayoutUtils manage an "exception" list to it's default token based discovery. And this would require some more UI to configure it... Nico. 2007/9/25, nicolas de loof <[EMAIL PROTECTED]>: > I've created http://jira.codehaus.org/browse/MRM-519 for this and > attached a patch. > > 2007/9/25, nicolas de loof <[EMAIL PROTECTED]>: > > I just installed beta-2 in replacement to my corporate repo. > > I may had better tested it before :-( > > > > requesting using maven1 an artifact with "-" in artifactID fails : > > > > request for "maven/plugins/maven-test-plugin-1.8.2.jar" > > in logs : > > <proxied>\maven\maven\test-plugin-1.8.2\maven-test-plugin-1.8.2.jar > > does not exist > > > > The versionUtil.versionPatterns seems to grab too much tags as possible > > version. > > > > I've patched it locally to remove "test[_.0-9]*" as possible version > > pattern. Could we enhance this artifactId detection by ensuring ALL > > tokens considered as version are valid versionElements ? > > > > Something like this : > > [- <artifactId-Element>]+ [- <versionElement>]+ [- <classifier>]? > > > > In such case, for "maven-test-plugin-1.8.2", as "plugin" is not a > > valid versionElement, "test" and "plugin" may have been added to the > > artifactId > > >
