[ http://jira.codehaus.org/browse/MRM-7?page=comments#action_40814 ] John Casey commented on MRM-7: ------------------------------
This is because the parsing process for the artifact information finds 'jdbc3' as a classifier...in which case, this handling is perfect. Unfortunately, in order to maintain some separation from the repository layout, we need to have an Artifact instance to feed to the ArtifactRepositoryLayout so that we can get the path of the corresponding POM. This is important so that we can [eventually] move into processing m2-repository sources as well as m1-repository sources. While I could add an exception to the version pattern (determines where the version spec ends and any classifier begins), you have to admit that 'jdbc3' is hardly a common version part. I have to admit, looking at the files in the repository, I'm not sure what this artifact is - and the POM for that artifact is of absolutely no help. I suggest that the name of this artifact be fixed, not the conversion process. > postgresql-7.4.1-jdbc3.pom badly converted > ------------------------------------------ > > Key: MRM-7 > URL: http://jira.codehaus.org/browse/MRM-7 > Project: Maven Repository Manager > Type: Bug > Components: repository-converter > Reporter: Carlos Sanchez > > > The m1 postgresql-7.4.1-jdbc3.pom was renamed to postgresql-7.4.1.pom in m2 -- 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 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
