|
»
»
renaming components/trunk to maven3/trunk?
|
View:
New views
7 Messages
—
Rating Filter:
Alert me
|
 |
renaming components/trunk to maven3/trunk?
by brettporter
::
Rate this Message:
Hi,
I did some of the branch and version maintenance I mentioned in the other mail. In the spirit of "fresh start", does it make sense for moving components/trunk to maven3/trunk in SVN? If so, would someone actively working on it like to make the move? It may make sense to also/instead shift maven 2.2 to a corresponding maven2/ tree (retaining anything in components for historical purposes, of course). Opinions? - Brett --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@... For additional commands, e-mail: dev-help@... |
|
|
Re: renaming components/trunk to maven3/trunk?
by John Casey-5
::
Rate this Message:
I think that the codebases are diverging enough that it makes sense to
separate them. I'd only say we should do this if we move both, though...and I guess we'd need to move the maven 2.x branches over with maven/* as well. +1 -john Brett Porter wrote: > Hi, > > I did some of the branch and version maintenance I mentioned in the > other mail. > > In the spirit of "fresh start", does it make sense for moving > components/trunk to maven3/trunk in SVN? If so, would someone actively > working on it like to make the move? > > It may make sense to also/instead shift maven 2.2 to a corresponding > maven2/ tree (retaining anything in components for historical purposes, > of course). Opinions? > > - Brett > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscribe@... > For additional commands, e-mail: dev-help@... > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@... For additional commands, e-mail: dev-help@... |
|
|
Re: renaming components/trunk to maven3/trunk?
by Benjamin Bentmann
::
Rate this Message:
Brett Porter wrote:
> In the spirit of "fresh start", does it make sense for moving > components/trunk to maven3/trunk in SVN? +0 There's already a maven-1 directory so for the sake of consistency I would expect "maven-X" instead of "mavenX". Benjamin --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@... For additional commands, e-mail: dev-help@... |
|
|
Re: renaming components/trunk to maven3/trunk?
by John Casey-5
::
Rate this Message:
Sure, that sounds fine for consistency. I do think this is a good idea
in concept, though. Benjamin Bentmann wrote: > Brett Porter wrote: > >> In the spirit of "fresh start", does it make sense for moving >> components/trunk to maven3/trunk in SVN? > > +0 > > There's already a maven-1 directory so for the sake of consistency I > would expect "maven-X" instead of "mavenX". > > > Benjamin > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscribe@... > For additional commands, e-mail: dev-help@... > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@... For additional commands, e-mail: dev-help@... |
|
|
Re: renaming components/trunk to maven3/trunk?
by Ralph Goers
::
Rate this Message:
On Jul 6, 2009, at 6:52 PM, Brett Porter wrote: > Hi, > > I did some of the branch and version maintenance I mentioned in the > other mail. > > In the spirit of "fresh start", does it make sense for moving > components/trunk to maven3/trunk in SVN? If so, would someone > actively working on it like to make the move? > > It may make sense to also/instead shift maven 2.2 to a corresponding > maven2/ tree (retaining anything in components for historical > purposes, of course). Opinions? > > - Brett > +1 to maven3/trunk or maven-3/trunk. Ralph --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@... For additional commands, e-mail: dev-help@... |
|
|
Re: renaming components/trunk to maven3/trunk?
by Jason van Zyl-5
::
Rate this Message:
I have a massive checkin coming and when I'm finished that I'll sync
up with Benjamin and swizzle the branches. On 7-Jul-09, at 2:44 PM, Ralph Goers wrote: > > On Jul 6, 2009, at 6:52 PM, Brett Porter wrote: > >> Hi, >> >> I did some of the branch and version maintenance I mentioned in the >> other mail. >> >> In the spirit of "fresh start", does it make sense for moving >> components/trunk to maven3/trunk in SVN? If so, would someone >> actively working on it like to make the move? >> >> It may make sense to also/instead shift maven 2.2 to a >> corresponding maven2/ tree (retaining anything in components for >> historical purposes, of course). Opinions? >> >> - Brett >> > > +1 to maven3/trunk or maven-3/trunk. > > Ralph > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscribe@... > For additional commands, e-mail: dev-help@... > Thanks, Jason ---------------------------------------------------------- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl http://twitter.com/SonatypeNexus http://twitter.com/SonatypeM2E ---------------------------------------------------------- What matters is not ideas, but the people who have them. Good people can fix bad ideas, but good ideas can't save bad people. -- Paul Graham --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@... For additional commands, e-mail: dev-help@... |
|
|
Re: renaming components/trunk to maven3/trunk?
by brettporter
::
Rate this Message:
On 08/07/2009, at 3:31 AM, John Casey wrote: > I think that the codebases are diverging enough that it makes sense > to separate them. I'd only say we should do this if we move both, > though...and I guess we'd need to move the maven 2.x branches over > with maven/* as well. So here's what I'm thinking: svn mkdir https://svn.apache.org/repos/asf/maven/maven-2 svn mkdir https://svn.apache.org/repos/asf/maven/maven-2/branches svn mkdir https://svn.apache.org/repos/asf/maven/maven-2/tags svn cp https://svn.apache.org/repos/asf/maven/components/tags/maven-2.2.0 https://svn.apache.org/repos/asf/maven/maven-2/tags (just as an additional reference) svn mv https://svn.apache.org/repos/asf/maven/components/branches/maven-2.2.x https://svn.apache.org/repos/asf/maven/maven-2/branches (adjust POMs for SCM) svn cp https://svn.apache.org/repos/asf/maven/maven-2/branches/maven-2.2.x https://svn.apache.org/repos/asf/maven/maven-2/trunk (adjust POMs for SCM and version to 2.3.0-SNAPSHOT) (retain components/ for all maven 2.0.x and 2.1.x releases) svn mkdir https://svn.apache.org/repos/asf/maven/maven-3 svn mkdir https://svn.apache.org/repos/asf/maven/maven-3/branches svn mkdir https://svn.apache.org/repos/asf/maven/maven-3/tags (Leaving here for Jason to move components/trunk over later) WDYT? - Brett --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@... For additional commands, e-mail: dev-help@... |
| Free embeddable forum powered by Nabble | Forum Help |
