Mailing-List: contact dev-help@maven.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Maven Developers List" <dev@maven.apache.org>
Received-SPF: pass (hermes.apache.org: local policy)
Message-ID: <00e801c4db75$5672fed0$211b03c2@cgeyfr.cgey.fr>
From: "Emmanuel Venisse" <emmanuel@venisse.net>
To: "Maven Developers List" <dev@maven.apache.org>
References: <1102283692.41b383acc46d5@mail.iinet.net.au>
Subject: Re: [proposal] Move Maven 1.x from CVS to Subversion
Date: Mon, 6 Dec 2004 10:24:07 +0100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit


----- Original Message ----- 
From: "Brett Porter" <brett@apache.org>
To: <dev@maven.apache.org>
Sent: Sunday, December 05, 2004 10:54 PM
Subject: [proposal] Move Maven 1.x from CVS to Subversion


> Hi,
>
> I'd like to start a discussion about this to see what people think.
>
> The reasons:
> - timing is right as we wind down MAVEN-1_0-BRANCH
> - HTTPS makes it more practical behind firewalls
> - the tool support seems to be mostly there now (not perfect, but good
enough)
> - is being encouraged ASF wide
>
> Proposed repositories to move:
> maven
> maven-plugins
> maven-plugins-sandbox
> maven-jelly-tags
>
> Proposed layout in svn:
> maven
>   maven-1
>     core (formerly maven)
>       trunk
>       branches
>       tags (hereafter abbreviated as t/b/t)
>     plugins
>       t/b/t
>     plugins-sandbox
>       t/b/t
>     jelly-tags
>       t/b/t
> (and later on...)
>   wagon
>     t/b/t
>   scm
>     t/b/t
>   components (or maven-2?)
>     maven-core
>       t/b/t
>     maven-model
>       t/b/t
>     ...
>
> Some points:
>
> * Why t/b/t at plugins level, not for individual plugins?
> easier to maintain the current structure, and plugins are infrequently
branched.
> When they are branched/tagged, they would be copied to, for example,
> maven-plugins/branches/java/1.5-SNAPSHOT/...
> The fact that this causes a different relative path to the extended parent
is
> problematic, so developing on the branch would require switcing your
checkout to
> the branch (which is possible), much like is done with CVS. I don't see an
easy
> way to avoid this (except for m2 style parent POM references :)
>
> * What about Maven's subversion support?
> The only remaining plugin missing support is maven-scm-plugin. I'm going
to look
> at adding it quickly, then revisit that plugin later to use maven-scm once
it is
> released.
>
> What do others think?

+1

Emmanuel


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org