www-infrastructure-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From John Casey <jdca...@commonjava.org>
Subject Re: Maven gitroots on Apache@Github
Date Fri, 10 Jul 2009 00:03:48 GMT
The affected mirror is:


Currently, the Maven 3.x source is still present in the structure 
mirrored there, but the Maven > 2.2.0 sources have moved. Where the 
original location was/is:


The Maven 2.2.1+ location is:


Going forward, the Maven 3.x location will move to:


However, we're still waiting for some developers to finish 
commits/merges in that code before renaming the URL(s).

So, in the end, I expect we'll need to split the maven/tree mirror into 
two or three parts:

* the existing /maven/components tree, which contains historical 

* the new Maven 2 tree at /maven/maven-2

* the new Maven 3 tree at /maven/maven-3

If any of this is unclear, let me know.



Jukka Zitting wrote:
> Hi,
> On Thu, Jul 9, 2009 at 11:20 PM, John Casey<jdcasey@commonjava.org> wrote:
>> Just a few minutes ago, we started the process of breaking up the
>> maven/components directory in SVN into maven/maven-2, maven/maven-3, etc.
>> This means that some of the gitroots on our github acct will be wrong, since
>> the core gitroot is configured to use maven/components.
>> Is there an easy way to reconfigure/clone that old gitroot to use the new
>> locations, or do we need to scrap the old one and generate a new set? If we
>> need to generate a new set, is there any magic to doing that?
> We have some tools for handling such cases. Could you list all the
> affected Git mirrors and describe the respective svn changes for each
> of those mirrors?
> BR,
> Jukka Zitting

View raw message