You're going to wrong way.
Pass into your Ant build the version number like so: ant
-Dversion=XX.YY.ZZ clean build test.
Then use the task to replace a token in your Java file. Even
better, you store that number in MANIFEST.MF and update it with the
task. Or, use a properties file. That way
Does anybody know If I set the "timeout" attribute on the junit task to
zero, will the timeout value be infinite?
Thanks,
Robert
Look into the buildnumber tag and try to tie your buildnumber to your tag.
ant-contrib has a Math tag for handling the arithmetic.
Or just keep a tag.properties file in your source.
>From an SCM point-of-view, you should tell CVS what you want, not the
other way around.
Robert
"KrustyDer
When I build the code base, I'm able to get a change list before the
build. My developers are asking me to include a special entry in the
MANIFEST.MF files for our JAR's that tracks the version of the JAR, but is
not the build number. For example, the first time I run a build, the
MANIFEST.MF w
Don't forget that it makes a great installer framework and tasty breakfast
spread.
Robert
[EMAIL PROTECTED]
09/29/2004 04:56 AM
Please respond to
"Ant Users List" <[EMAIL PROTECTED]>
To
"Ant Users List" <[EMAIL PROTECTED]>
cc
Subject
Re: ANT capabilities question
I am currently wri
The xsd files are 09/28/2004 09:19 AM and the resulting java files are
09/28/2004 09:45 AM. Thus, if I rebuild, I would expect them to skip the
xjc task. However, that's not the case.
dont.jaxb.compile is a property the user can set to skip the jaxb compile.
I have a similar property for all
