Well, maybe not a 'hack' in the true sense of the word ;), but it will be weird having to commit and 'svn up' any change made in build/ to see it locally in the svn:external-ized build/ locations. I know that won't have to happen very often once we are stable again, but it will cause a lot of confusion up front.
No matter how many times this gets discussed and reminded, someone will make a change to one of the build/ copies (not realizing it will affect them all) and effectively hose the entire build process till that change gets reverted. You can count on it. Although that's not really enough to stop us from going ahead with it.
I am definitely -1 on having duplicate files and config stuff everywhere. Your suggestion is probably the best solution.
So, that said, let's move forward with it. I've already made a lot of local changes that I'll have to fix, but it should be relatively painless.
-- James Mitchell Software Engineer / Open Source Evangelist EdgeTech, Inc. 678.910.8017 AIM: jmitchtx
----- Original Message ----- From: "Martin Cooper" <[EMAIL PROTECTED]>
To: "Struts Developers List" <dev@struts.apache.org>
Sent: Sunday, February 20, 2005 3:13 AM
Subject: Re: Building Struts
On Sat, 19 Feb 2005 15:04:34 -0500, James Mitchell <[EMAIL PROTECTED]> wrote:That seems like quite a hack
I'd be interested to hear why you feel this way. It's actually pretty much the exact scenario for which svn:externals were created, and, I think, somewhat more in line with the expected usage of that functionality that the whole 'current' thing is. ;-)
-- Martin Cooper
and going to be a bit awkward to the unsuspecting user/developer. But I honestly don't have a better option right now. I've already started the process of consolidating the various common maven configuration stuff. I'll be checking things in this weekend and next week.
-- James Mitchell Software Engineer / Open Source Evangelist EdgeTech, Inc. 678.910.8017 AIM: jmitchtx
----- Original Message ----- From: "Martin Cooper" <[EMAIL PROTECTED]> To: "Struts Developers List" <dev@struts.apache.org> Sent: Saturday, February 19, 2005 1:03 PM Subject: Re: Building Struts
> On Sat, 19 Feb 2005 10:25:02 -0600, Joe Germuska <[EMAIL PROTECTED]> > wrote: >> >> 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. > > Yes, you're right. We will need to tell Maven to include the build > directory. But that should be pretty straightforward. > > If everyone's OK with this, I'll have a go at it tomorrow, if nobody > beats me to it. (I'll be out all day today, starting about 5 minutes > from now ;). > > -- > Martin Cooper > > >> >> (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 > > --------------------------------------------------------------------- > 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]
