[ http://jira.codehaus.org/browse/MNG-321?page=comments#action_37845 ]
John Casey commented on MNG-321:
--------------------------------
are we also excluding the ${version} directory for poms, or only the
${artifactId} dir?
It's a difference between these results (from example given):
org/apache/maven/2.0-alpha-1/maven-2.0-alpha-1.pom (with version dir)
and
org/apache/maven/maven-2.0-alpha-1.pom (without)
Once we answer this, it's a [relatively] simple matter of changing the
DefaultArtifactLayout's pathOfMetadata(..) method.
> 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: John Casey
> 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]
