Regarding the Ant way... I could do what I want just by not defining a given property in my properties file, that would be acceptable. However, I encountered a problem doing that...
The first task in my build bumps up a build number in the properties file. In doing so, it seems that any comments in the properties file are wiped out. I wouldn't want to do conditionals this way unles I could have a comment that says "uncomment this for build type A, comment it for type B". So, is there a way to get this task... <propertyfile file="build.properties"> <entry key="build_number" default="0" type="int" operation="+" value="1" pattern="0000" /> </propertyfile> To NOT wipe out my comments? Thanks again, I'm learning alot :) -- Frank W. Zammetti Founder and Chief Software Architect Omnytex Technologies http://www.omnytex.com On Mon, February 28, 2005 1:07 pm, Matt Benson said: > > --- "Frank W. Zammetti" <[EMAIL PROTECTED]> wrote: >> Is it possible, and if so how, to do conditionals? >> I'd like to have a way >> basically on each task to say "if property A=value1, >> then run this task, >> otherwise don't". I'm looking through the manual >> now but haven't come >> across what seems to fit the bill. > > As others have suggested, you can use ant-contrib's if > task. However, the "Ant way" to do this is described > in the manual: > http://ant.apache.org/manual/using.html#buildfile > > HTH, > Matt > > __________________________________________________ > Do You Yahoo!? > Tired of spam? Yahoo! Mail has the best spam protection around > http://mail.yahoo.com > > --------------------------------------------------------------------- > 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]
