On Wed, 16 Mar 2005, Rainer Noack wrote:
> I'm not really sure what you mean.
> Either you have one "boolean" property that tells you cfg has changed or not
> Or you have two properties with last and current cfg.
> [...]
Thanks a lot! The second approach just works nicely for me :-)
...only jar the files...
...jar and sign...
Jan
> -Ursprüngliche Nachricht-
> Von: Rainer Noack [mailto:[EMAIL PROTECTED]
> Gesendet am: Mittwoch, 16. März 2005 22:56
> An: 'Ant Users List'
> Betreff: RE: Creating new JARs based on property change
> Sent: Wednesday, March 16, 2005 5:52 PM
> To: Ant Users List; [EMAIL PROTECTED]
> Subject: Re: Creating new JARs based on property change
>
>
> On Wed, 16 Mar 2005, Rainer Noack wrote:
>
> > Remove the existing jar.
>
> Sure, but I only want to remove the ex
On Wed, 16 Mar 2005, Rainer Noack wrote:
> Remove the existing jar.
Sure, but I only want to remove the existing JAR if the property indicating
whether the JAR is supposed to be signed has changed since otherwise I end
up rebuilding the JAR file even though it wasn't necessary.
This property is s
Remove the existing jar.
Cheers
Rainer
> -Original Message-
> From: Holger Rauch [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, March 16, 2005 4:43 PM
> To: user@ant.apache.org
> Subject: Creating new JARs based on property change
>
>
> Hi!
>
> In my build
Hi!
In my build file I have a property telling whether JARs are supposed to be
signed using or not. Furthermore, there's on uptodate check based
on whether any of the JAR file's contents are more recent than the JAR file
itself.
How can I enforce rejarring of a JAR file when the property indicat
