RE: [proposal] Move Maven 1.x from CVS to Subversion
-Original Message- From: Brett Porter [mailto:[EMAIL PROTECTED] Sent: Sunday, December 05, 2004 10:55 PM To: [EMAIL PROTECTED] 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 +1 Michal - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [proposal] Move Maven 1.x from CVS to Subversion
- Original Message - From: Brett Porter [EMAIL PROTECTED] To: [EMAIL PROTECTED] 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [proposal] Move Maven 1.x from CVS to Subversion
- Original Message - From: Alex Karasulu [EMAIL PROTECTED] To: Maven Developers List [EMAIL PROTECTED] Sent: Sunday, December 05, 2004 11:09 PM Subject: Re: [proposal] Move Maven 1.x from CVS to Subversion Hiya, +1 Really the timing as U said sounds about right. Also this helps progress the use and development of the SCM plugin. BTW there was a pure Java SVN client in the works out there. Down the road it might be useful for adding more SCM goals to beef up the plugin: http://tmate.org/svn/ Excellent information. Trygve, I think we can use it. The license is BSD-like Emmanuel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [proposal] Move Maven 1.x from CVS to Subversion
Ok, every seems pretty keen on this. I'll start investigating the necessary steps. In the mean time, if anyone has any different preferences for the layout, please say so. Cheers, Brett Brett Porter wrote: 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? Cheers, Brett - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [proposal] Move Maven 1.x from CVS to Subversion
On man, 2004-12-06 at 10:36, Emmanuel Venisse wrote: - Original Message - From: Alex Karasulu [EMAIL PROTECTED] To: Maven Developers List [EMAIL PROTECTED] Sent: Sunday, December 05, 2004 11:09 PM Subject: Re: [proposal] Move Maven 1.x from CVS to Hiya, +1 Really the timing as U said sounds about right. Also this helps progress the use and development of the SCM plugin. BTW there was a pure Java SVN client in the works out there. Down the road it might be useful for adding more SCM goals to beef up the plugin: http://tmate.org/svn/ Excellent information. Trygve, I think we can use it. The license is BSD-like Yep, I've already noted it down. -- Trygve Emmanuel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [proposal] Move Maven 1.x from CVS to Subversion
On man, 2004-12-06 at 12:26, Brett Porter wrote: Ok, every seems pretty keen on this. I'll start investigating the necessary steps. In the mean time, if anyone has any different preferences for the layout, please say so. I'd like to make sure this will be compatible with the artifact path from maven 2 before we go ahead with this. I don't think having all the plugins share the same tag/branch catalogs is going to work well with the artifact path idea. We can talk about the details on IRC when you're around and post the results. -- Trygve Cheers, Brett Brett Porter wrote: 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? Cheers, Brett - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[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? Cheers, Brett - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [proposal] Move Maven 1.x from CVS to Subversion
I would be +1 for moving to subversion. I have been using svn on Cargo (codehaus) for 1-2 months and I'm very happy. The only downside on codehaus I can think of is that we're using svn+ssh as the protocol which is not very well supported by the different tools (except TortoiseSVN which is very nice). Dunno about HTTPS support. Thanks -Vincent -Original Message- From: Brett Porter [mailto:[EMAIL PROTECTED] Sent: dimanche 5 décembre 2004 22:55 To: [EMAIL PROTECTED] 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? Cheers, Brett - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [proposal] Move Maven 1.x from CVS to Subversion
Hiya, +1 Really the timing as U said sounds about right. Also this helps progress the use and development of the SCM plugin. BTW there was a pure Java SVN client in the works out there. Down the road it might be useful for adding more SCM goals to beef up the plugin: http://tmate.org/svn/ Cheers, Alex Brett Porter wrote: 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? Cheers, Brett - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [proposal] Move Maven 1.x from CVS to Subversion
On Sun, 2004-12-05 at 13:54, Brett Porter wrote: 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 +1 The only thing to keep in mind for m2 is that the directory in which an artifact build resides must be the same as the artifactId. It's really only important for m2 but allows the unified source tree (USD) to function and allows the proper creation of an artifact path which is used in continuum to derive the correct SCM path for a child project where the only definition for the entire group of projects is in the top-level parent POM. -- jvz. Jason van Zyl [EMAIL PROTECTED] http://maven.apache.org happiness is like a butterfly: the more you chase it, the more it will elude you, but if you turn your attention to other things, it will come and sit softly on your shoulder ... -- Thoreau - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [proposal] Move Maven 1.x from CVS to Subversion
+ 1 (even though I haven't played enough with svn yet...) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [proposal] Move Maven 1.x from CVS to Subversion
On søn, 2004-12-05 at 22:54, Brett Porter wrote: 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 -- Trygve Cheers, Brett - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [proposal] Move Maven 1.x from CVS to Subversion
+1 I tested it with cargo and I find SVN very good. Arnaud -Message d'origine- De : Brett Porter [mailto:[EMAIL PROTECTED] Envoyé : dimanche 5 décembre 2004 22:55 À : [EMAIL PROTECTED] Objet : [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? Cheers, Brett - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
