Re: Nested "manifest" element inside "jar" task.

[Conor MacNeill]

David McLeod wrote:

Now, the jar file is created EVERY TIME, even though none of the class files
have changed!  It doesn't make sense; ant should not even get inside the
<jar> task unless the class files have been touched, but it seems as if the
inclusion of the <manifest> sub-element creates an internal dependency that
I cannot control.

The manifest is considered as much a part of the Jar as the classes in the Jar. As such, the new manifest is checked against the existing manifest to see if it has changed. In your case, since the value of the manifest is always changing the jar is always updated. You will need to use <uptodate> to control whether to run the <jar> task, setting up a relationship betweem the jar and the classes.

Conor


--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>