-----Original Message----- From: Vincent Massol [mailto:[email protected]] Sent: jeudi 28 septembre 2006 12:21 To: [email protected] Subject: RE: [xwiki-dev] Ok to use svn:externals?
-----Original Message----- From: Vincent Massol [mailto:[email protected]] Sent: jeudi 28 septembre 2006 12:10 To: '[email protected]' Subject: RE: [xwiki-dev] Ok to use svn:externals?
-----Original Message----- From: jeremi joslin [mailto:[email protected]] Sent: jeudi 28 septembre 2006 11:48 To: [email protected] Cc: [email protected] Subject: Re: [xwiki-dev] Ok to use svn:externals?
Hi vincent, I've look at this function for the subproject GELC. The problem is I don't think it's possible to use it for getting the projet and for commiting.
We can't use it for commits because we don't use the same URL for commiters(developpers are over ssh) and users (over svn protocol).
I understand your point now. I'm checking if there's a way to have a single trunks/ dir. Otherwise the alternative is to have 2: one for committers and one for anonymous users. Or we can decide that the trunks/ dir is only for committers. WDYT?
I'll get back to you after I do some experiments.
Ok as you said there's no way to have both definitions in one svn:externals definition unless you're using the https protocol.
Thus I modify my proposal to have:
trunks-users/ (uses svn protocol) trunk-devs/ (uses svn+ssh protocol)
I meant trunks-devs/ (note the 's') -Vincent
PS: Of course the best would be to have a https:// protocol as we have @ Apache.
On 9/28/06, Vincent Massol <[email protected]> wrote:
Hi developers,
Right now it's pretty painful to checkout xwiki trunks. You have to
do it
one by one manually (xwiki/trunk, xwiki-apps/, xwiki-clients/, xwiki-plugins/emailnotification/trunk, etc).
I'd like to create a trunks/ directory in svn://svn.forge.objectweb.org/svnroot/xwiki and create some svn:externals definitions so that anyone doing a checkout of svn://svn.forge.objectweb.org/svnroot/xwiki/trunks will get all the svn trunks checked out in one go (see http://svnbook.red-bean.com/en/1.0/ch07s03.html if you don't know what svn:externals are). This is a pretty standard way of using subversion done by lots of projects I know.
Here's what I suggest as svn:externals definitions for trunks/:
xwiki svn://svn.forge.objectweb.org/svnroot/xwiki/xwiki/trunk
xwiki-apps/agilepm svn://svn.forge.objectweb.org/svnroot/xwiki/xwiki-apps/agilepm
xwiki-apps/gelc/gelcv1 svn://svn.forge.objectweb.org/svnroot/xwiki/xwiki- apps/gelc/gelcv1/trunk
xwiki-clients svn://svn.forge.objectweb.org/svnroot/xwiki/xwiki-clients
xwiki-plugins/emailnotification svn://svn.forge.objectweb.org/svnroot/xwiki/xwiki- plugins/emailnotification/trunk
xwiki-plugins/lucene svn://svn.forge.objectweb.org/svnroot/xwiki/xwiki- plugins/lucene/trunk
xwiki-plugins/task-manager svn://svn.forge.objectweb.org/svnroot/xwiki/xwiki-plugins/task- manager
xwiki-sandbox svn://svn.forge.objectweb.org/svnroot/xwiki/xwiki-sandbox
xwiki-tools svn://svn.forge.objectweb.org/svnroot/xwiki/xwiki-tools
Let me know if this is fine and I'll create it (provided I still have right access to the repo).
Thanks
-Vincent
PS: We'll also need to rationalize the trunk/, branches/ tags/ directory a bit better I think but that's for later J
___________________________________________________________________________ D�couvrez un nouveau moyen de poser toutes vos questions quelque soit le sujet ! Yahoo! Questions/R�ponses pour partager vos connaissances, vos opinions et vos exp�riences. http://fr.answers.yahoo.com