Hi, Stefan. Thank you for your answer.
I do have an ant script that creates and signs jars. But it does it always, even if it is not required (no files have changed). The script does other things also, and I'd like to save the time to generate and sign something that has not changed. You say <signjar> can sign jars only if they were changed - and this by using the signedjar option? How this? I have not yet tried to write my own task, as this job is actually very generic and should be in the distribution somehow. The task I think of looks like: <if-modified runtarget="name_of_target_that_creates_and_signs_jar" comparedto="signed.jar"> <fileset ...> </fileset> </if-modified> I can also think of running all other tasks nested within the if-modified element. That should solve the problem and be flexible enough to not only create signed jars. What do you think? Hiran > -----Ursprüngliche Nachricht----- > Von: Stefan Bodewig [mailto:[EMAIL PROTECTED]] > Gesendet: Montag, 7. Oktober 2002 10:49 > An: [EMAIL PROTECTED] > Betreff: Re: Conditional Execution > > > On Mon, 7 Oct 2002, Software AG <[EMAIL PROTECTED]> wrote: > > > Does anyone know how to perform conditional execution, just like the > > javac task does it? > > Write (or use) a task to do so. > > > I want to create and sign jars, but if and only if the content has > > changed (file time is sufficient). > > <jar> will take care of the create part, using <signjar>'s signedjar > attribute should make it only sign new jars. > > Stefan > > -- > To unsubscribe, e-mail: > <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
