Re: svn commit: r149171 - in jakarta/commons: proper/commons-build/trunk/ sandbox/cli/trunk/ sandbox/codec-multipart/trunk/ sandbox/compress/trunk/ sandbox/compress/trunk/xdocs/ sandbox/contract/trunk/ sandbox/contract/trunk/xdocs/ sandbox/convert/trunk/

[Dirk Verbeeck]

I know this is only a small improvement from the previous situation. 
If you do an individual checkout you still have to make sure you have 
the correct path to a commons-build directory.
Is there a better way to include global information?

-- Dirk
Tim O'Brien wrote:
Innovative use of svn:externals, but it does also mean that the only way
to build a project with maven is to do so using the trunks-proper or
trunk-sandbox directory.
This is fine, as long as people know to use svn switch when they want to
build an old tag:
So, if you want to build an old tag, and you have a checked out the
trunks-proper, you'll need to switch to the tag before you do such a
thing.  The only question this then raises is, if you were to then do an
svn update from the trunks-proper directory, would the svn:externals
pointing to trunk switch you back to the trunk?
Tim

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]