On Tue, 22 Feb 2005 09:49:52 +0100, Mark Lowe <[EMAIL PROTECTED]> wrote: > Sorry if this sound stupid, I cant find the url that svn requires to > checkout shale et al.
http://struts.apache.org/acquiring.html#SourceCode -- Martin Cooper > I saw that someone mentioned flowscript unit > testing, I'm working on a cocoon project and I'd like to see if > there's a way of testing the flowscripts we have. > > Mark > > > On Mon, 21 Feb 2005 11:28:04 -0800, Don Brown <[EMAIL PROTECTED]> wrote: > > Martin Cooper wrote: > > <snip /> > > > OK, I've created a build subproject, with trunk / tags / branches, > > > added it to 'current', and also added it to the following subprojects: > > > apps, bsf, core, el, faces, taglib, tiles. I have *not* added it to: > > > flow, sandbox, shale. Certainly shale uses a separate build system, > > > but should I go ahead and add it to flow and sandbox? > > > > Sure, flow's build was copied right from bsf. Flow does have a custom > > run-tests Ant task which uses a homegrown Javascript unit testing > > framework. It also has two other tasks for building the two example > > applications. I believe Maven can use Ant tasks, but I have no idea how. > > > > Thanks for the hard work. > > > > Don > > > > > > > > I added a little README file that tries to explain what the deal is > > > with this showing up in multiple places. With any luck, some people > > > will actually read it. ;-) > > > > > > -- > > > Martin Cooper > > > > > > > > > > > >>-- > > >>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] > > >> > > >> > > > > > > > > > --------------------------------------------------------------------- > > > 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] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
