I helped implement the svn:externals over in commons, and it does seem like it is working well.
Brett your concern about anon and auth URLs is true. In commons we decided to optimize for the committer and user https. I would like to see svn:externals support some mechanism for using the scheme used to checkout, and I'd also like to see ViewCVS have the ability to view directories stored in svn:externals. There is some conceptual discontinuity between CVS and SVN. Whereas in CVS you would checkout an entire module, if you were to do such a thing in SVN you would retrieve every tag and branch. This leaves you with two alternatives, come up with a creative linking mechanism like svn:externals, or write a script that checks out the right version of every component. I've started approaching multi-project Maven projects using svn:externals because it allows you to avoid the question of where to tag or branch. Every deliverable has a tags and branches directory and multi-project POM extension is accomplished in a tree constructed with svn:externals. This way you can use the same multi-project structure and point to different tags and branches accordingly. But, Brett, yes, it still feels a bit strange. Tim -----Original Message----- From: Vincent Massol [mailto:[EMAIL PROTECTED] Sent: Mon 1/31/2005 1:25 AM To: 'Maven Developers List' Subject: RE: Setting svn:externals for maven-1? I'm far from being an expert in this domain. I just happen to have checked out Jakarta commons and commons-sandbox this week end and I was really glad they decided to have a svn:externals definition. Otherwise I would have had to check out each project one by one... :-) Of course we currently only have 4 projects in maven-1 so that's still manageable by hand. Thanks -Vincent > -----Original Message----- > From: Brett Porter [mailto:[EMAIL PROTECTED] > Sent: dimanche 30 janvier 2005 23:39 > To: Maven Developers List > Subject: Re: Setting svn:externals for maven-1? > > Not really. It feels like a bit of a hack to me. > > I'd prefer to work on making things actually build independantly of the > checked > out structure (too much reliance on ../something in the current build). > > There are limitations with svn:externals: > - In an environment where http is anon and https is auth, which do you use > in > the externals definition? Unless I'm missing something, you'd have to make > an > anon copy of it. > - its an unnecessary maintenance headache > - you then have two structures that could potentially be in play, adding > the > risk of people having problems > - when you develop on a branch, you either need to manually switch part of > the > checkout, or it works completely differently again. > > If you disagree or have other suggestions for ways to improve it, please > let me > know. I really haven't wrapped my head around the best way to make it > work, > especially in multiproject scenarios. > > Cheers, > Brett > > Quoting Vincent Massol <[EMAIL PROTECTED]>: > > > Hi guys, > > > > Is it planned to set up some svn:externals for > > https://svn.apache.org/repos/asf/maven/maven-1/? > > > > I think that would help checking out/updating everything related to > maven-1 > > in one go. They've done this for Jakarta commons > > (https://svn.apache.org/repos/asf/jakarta/commons/, trunks-proper and > > trunks-sandbox). > > > > Thoughts? > > > > Thanks > > -Vincent > > > > > > > > --------------------------------------------------------------------- > > 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] _________________________________________________________________ Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français ! Yahoo! Mail : http://fr.mail.yahoo.com --------------------------------------------------------------------- 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]
