> -----Original Message----- > From: Martin Cooper > Sent: Monday, December 28, 2009 15:10 > To: Struts Developers List > Subject: Re: XWork has landed! > > On Mon, Dec 28, 2009 at 11:37 AM, Wes Wannemacher > <[email protected]> wrote: > > On Mon, Dec 28, 2009 at 2:16 PM, Paul Benedict > <[email protected]> wrote: > >> Having XWork as a separate module is actually preferred, but only > >> because it's a better design decision. It will create a clear <snip/> > > As I see it, we have a set of choices to make > > 1) (a) move, (b) copy, (c) create an 'external' reference for > 2) (a) all of XWork, (b) just the XWork core, (c) some other > subset of XWork > 3) (a) to a peer of 'struts2', (b) to somewhere within > 'struts2', (c) to somewhere else > > I believe 1c + 2a + 3a = what we have today except that it's > one checkout instead of two. With that option, nothing about > the build or the build documentation changes, AFAICT. Is that > what we want? I don't know, I'm just suggesting that it's a > low-cost way of moving forward now that the code is in our repo. > > I don't have a particular bias in regard to how we go about > this, beyond some source control best practices. I just think > we need to make sure we're all on the same page about where > we want to end up. >
I think it would be best to have in the same source control repository, but keep it as separate as possible. We use the following tree here: /repoPerProjectGroup ./trunk ../subproject1 ../subproject2 ../subproject3 ./branches ./common ./private ./releases ./tmp Allowing subprojects to be freely independent and dependent at the same time. -Jason -- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- - - - Jason Pyeron PD Inc. http://www.pdinc.us - - Principal Consultant 10 West 24th Street #100 - - +1 (443) 269-1555 x333 Baltimore, Maryland 21218 - - - -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- This message is copyright PD Inc, subject to license 20080407P00. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
