On Wed, 30 Oct 2002, David Graham wrote: > Date: Wed, 30 Oct 2002 20:32:31 -0700 > From: David Graham <[EMAIL PROTECTED]> > Reply-To: Struts Developers List <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Subject: Building Struts > > I'm starting to work on source patches so I'm setting up my build > environment for testing purposes. I've found this exercise both mundane and > time consuming. Would it be worthwhile to post a zipped up build > environment with a build.properties that's ready to go? Getting all the > appropriate jars and setting the paths is the main problem. > > This would get new developers up and running immediately and maybe promote > more involvement. If I'm the only one that feels this way, then it's not > worthwhile (and maybe I'm going about it wrong). >
There is a reason that build.properties is *not* included in the download -- there is no single way to organize your environment, so there is no one common build.properties script that could ever suffice. Just as one trivial example, I can't even use the same build.properties file on my Linux development system and my Win2K based laptop, because the syntax of absolute paths is different. We've already got a roadmap item for evaluating a switch to Maven for 1.2, which (among other things) deals with this issue (although that comes with its own complexities). I don't want to disrupt things pre 1.1-final, and I can guarantee you that severe messing with build.xml would be disruptive :-). Dealing with the build environment sounds like a very good *first* step as soon as we branch the 1.1 codebase and start using the HEAD branch for 1.2. > David > Craig -- To unsubscribe, e-mail: <mailto:struts-dev-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:struts-dev-help@;jakarta.apache.org>
