You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "Brett Porter (JIRA)" <ji...@codehaus.org> on 2005/04/16 10:15:21 UTC
[jira] Created: (MNG-321) when packaging = pom, the repository should store it in the groupID directory
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
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
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Commented: (MNG-321) when packaging = pom, the repository
should store it in the groupID directory
Posted by "John Casey (JIRA)" <ji...@codehaus.org>.
[ 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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Closed: (MNG-321) when packaging = pom, the repository should store it in the groupID directory
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-321?page=all ]
Brett Porter closed MNG-321:
----------------------------
Fix Version: (was: 2.0-alpha-2)
Resolution: Won't Fix
> 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
>
>
> 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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Commented: (MNG-321) when packaging = pom, the repository should store it in the groupID directory
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-321?page=comments#action_38006 ]
Brett Porter commented on MNG-321:
----------------------------------
what's really needed is for the repo tool to process the m2 repo in place, adding extra poms, md5s, etc - but this is going to take more work which we can leave for the repository project itself.
I've whipped up a shell script to do the conversion in the repo, so can finish this one off.
> 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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Commented: (MNG-321) when packaging = pom, the repository should store it in the groupID directory
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-321?page=comments#action_38008 ]
Brett Porter commented on MNG-321:
----------------------------------
where this will presently fall down is the difference in snapshot location. This isn't a major flaw, and we can live with it until alpha-3 when the old poms can be removed
> 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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Commented: (MNG-321) when packaging = pom, the repository should store it in the groupID directory
Posted by "John Casey (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-321?page=comments#action_37959 ]
John Casey commented on MNG-321:
--------------------------------
this has to be resolved in a very specific order:
1. make the change on localhost/localrepo
2. install repoclean instance with new version of maven-artifact
3. run tests
4. sync new repoclean instance with [temp] instance on beaver
5. perform conversion of to-ibiblio/maven2 to temp repo location
6. change super-pom repository to point at temp repo
7. clear local repository
8. bootstrap m2 using temp remote repo
9. restore super-pom repository specification
10. swap temp repo with "real" /maven2 dir
11. sync new /maven2 dir with ibiblio
12. re-bootstrap m2 with new layout on ibiblio
13. commit changes
14. verify CI
NOTE: changes must be made to the DefaultRepositoryLayout class in maven-artifact, as well as the layout used in MBoot2 and [possibly] in the core-it-verifier.
> 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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Commented: (MNG-321) when packaging = pom, the repository should store it in the groupID directory
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ 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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org