I will second Steve's recommendation. We started using ant here as a developer's build tool. As we try to move toward a nightly automated build type of environment, I have found that it is essential to name the various properties and tasks identically, with identical meanings in the individual projects' build files. The nice part about fixing this is that a name is just a name. An individual build file that worked with a bunch of idiosyncratic names can easily be made to work using the standardized names. But it's almost impossible to do a uber-build file with the individual files have non-standardized names.
-----Original Message----- From: Steve Loughran [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 19, 2001 12:38 AM To: Ant Users List Subject: Re: Proper use of <uptodate> (a little off-topic) I would recommend you have separate deploy build files for each target, using similarly named parameters (deploy.warfile, deploy.host ...) and then call these targets from your main file using <ant>. This keeps things more controllable. The cactus project has some examples ----- Original Message ----- From: "DONNIE HALE" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, December 18, 2001 14:20 Subject: Re: Proper use of <uptodate> (a little off-topic) As far as deployment goes, I started down that track using ant. However, we have four different environments that we can deploy to; and trying to conditionally do the right thing for each from a single file is more procedural than declarative. Using WebLogic's command-line deployment tools is just a simple execution of "java" with the right command line. It took about a 25-line shell script, most of it for checking errors, to get what I wanted in a lot more straightforward manner than trying to do it in ant. For our NT platform, I've got an ant target that just does an <exec> on our deploy.cmd file. Hope that helps, Donnie -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
