I am not really familiar with svn:externals, but it sounds great. I'm not 100% sure that (2) is true, at least, if we're going to use maven dist to build distros. But even if we have to do a little, it will be much more straightforward.

(for those who are interested:
Chapter 7. Advanced Topics: Externals Definitions
http://svnbook.red-bean.com/en/1.1/ch07s03.html
)

I'm +1 on this approach. From the tail end of the page from the SVN book, it looks like we'll have to be conscious of some issues if we do any future repository re-orgs, but hopefully we won't have to.

Joe


At 7:43 AM -0800 2/19/05, Martin Cooper wrote:
By using svn:externals, we gain several things:

1) We get a "free" copy of 'build' along with each subproject, meaning
that it doesn't have to be checked out separately to build one
subproject. Checking out 'core', for example, would be enough to build
core.

2) The "free" copy means that we don't have to do anything special
when building the source distros, since the 'build' directory will
already be part of the checked out subproject when the distro is being
created.

3) We don't have to mess with Maven properties to deal with two
different build scenarios (i.e. checked out vs. source distro).

4) It's really simple! :-)

WDYT?


--
Joe Germuska [EMAIL PROTECTED] http://blog.germuska.com "Narrow minds are weapons made for mass destruction" -The Ex

Reply via email to