I used java interfaces - basically I just invoke the jvm like the batch or shell script would, except that I use ant, and load all the classpath and JVM settings via properties. The server or host-specific stuff I load through an include (which only has 2 or three host specific settings which rarely or never change) so that my startup build file can be moved from Windows (development) through Unix (production) with no changes at all. I do the exact same thing with the build.xml for the source code.
I'll post an example later tonight when I get home, don't have the script with me. Edward Wittmann Are you using the bea supplied ant tasks or using java interfaces (weblogic.Server, weblogic.Deployer, etc)? We're currently tracking down some subtle issues (though they are cross platform issues) which helps to identify by using ant. > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Sent: Tuesday, December 07, 2004 1:06 PM > To: Ant Users List > Subject: Re: using ant for non-java builds? > > > I happen to use Ant to start BEA weblogic - all my startup > parameters, > classpaths, etc, are in the file. Makes moving environment variables > between different environments really easy. > > > > Edward Wittmann > > > > --- Derek Haskin <[EMAIL PROTECTED]> wrote: > [SNIP] > > I am wondering if anyone has any experience in > > automating builds in ant for > > non-java based applications and if they would > > recommend using ant or not. > > I have said it before and I'll say it again. Ant > works great for nearly anything including building > non-Java applications. Besides, what could be more > fun than dragging your non-Java coworkers kicking and > screaming into the Java world? > > > > > If feasable I may end up using a combination of perl > > and ant scripts. > > > > What's the perl for? > > > thanks. > > > -Matt > > > > __________________________________ > Do you Yahoo!? > Yahoo! Mail - Find what you need with new enhanced search. > http://info.mail.yahoo.com/mail_250 > > --------------------------------------------------------------------- > 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]
