[ http://jira.codehaus.org/browse/MNG-321?page=comments#action_38012 ] Brett Porter commented on MNG-321: ----------------------------------
ok, did this - and have backed it out because of the changes to maven-artifact required. IT can't deal with the duality of "pom" artifact vs "pom" metadata. It should, and will - but not yet. I'm also skeptical about whether this is really the right thing to do. We might be reintroducing a problem with scalability when we start putting snapshots in one directory again. Let's hold off on this for the moment - on the upside, related things are more robust now :) > when packaging = pom, the repository should store it in the groupID directory > ----------------------------------------------------------------------------- > > Key: MNG-321 > URL: http://jira.codehaus.org/browse/MNG-321 > Project: m2 > Type: Bug > Components: repository-tools, maven-artifact > Reporter: Brett Porter > Assignee: Brett Porter > Priority: Blocker > Fix For: 2.0-alpha-2 > > > eliminate the artifactId from the path when packaging is pom, so the > repository matches the source tree and is easier to browse, avoiding > directories like: > org/apache/maven/maven/maven-2.0-alpha-1.pom > To allow migration, we should have the repo tools copy these into both > locations if found in either, then stop that and clean up at the release of > alpha-3 (allowing users to remain a release behind). -- 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]
