On 1/6/06, Jeffrey E Care <[EMAIL PROTECTED]> wrote:
> The jar task already figures this out for you.
Indeed it does. If Jar runs anyway, it could be because you generate a
manifest dynamically, with a date or version number that changes on
every build, forcing jar to always run. Otherwise is a "
Steve,
The jar task compares the timestamps of all the files you wish to jar to the
preexisting complete jar (if it had been run before) and will not execute if
none of them are later than the timestamp of the existing jar. Working
backwards from there you have the javac task which compares the
I would look at uptodate
http://ant.apache.org/manual/CoreTasks/uptodate.html
That would test file timestamps and set a property.
I am not sure what you want to do.
--glenn
On 1/6/06, Steve Roy <[EMAIL PROTECTED]> wrote:
> Hello,
>
> I have been using Ant for about a year but I still feel like I
The jar task already figures this out for you.
--
Jeffrey E. Care ([EMAIL PROTECTED])
WebSphere v7 Release Engineer
WebSphere Build Tooling Lead (Project Mantis)
Steve Roy <[EMAIL PROTECTED]> wrote on 01/06/2006 09:24:43 PM:
> Hello,
>
> I have been using Ant for about a year but I still feel
Hello,
I have been using Ant for about a year but I still feel like I am a
newbie, and maybe this explains my question, but you tell me.
I have a script where I compile the sources for my project and jar it
all up. This works well but I'm looking at adding an optimization where
the Jar task
