> Sadly it seems that the <manifest> entry is causing the rebuild
> of the JAR.
According to the doc, if you have use the <manifest> element, it checks
whether the build file is newer than the jar -- have you tried running
your target twice in a row without any build-file diddling in-between?
Neat concept. Wouldn't have caught me putting ${DSTAMP}${TSTAMP} in the
manifest, but it seems a good enough call.
Yes, I ran it a few times in a row --- it still did it...
I have:
06/20/2002 01:27p 352 build.xml
06/20/2002 01:53p 337 jar.jar
but I still get:
test:
fileset: Setup scanner in dir E:\data\test\src with patternSet{ includes: []
excludes: [] }
[jar] Updating jar since jar manifest has changed
[jar] Building jar: E:\data\test\jar.jar
[jar] adding directory META-INF/
[jar] adding entry META-INF/MANIFEST.MF
fileset: Setup scanner in dir E:\data\test\src with patternSet{ includes: []
excludes: [] }
after:
06/20/2002 01:27p 352 build.xml
06/20/2002 01:57p 337 jar.jar
Phew --- no diddling in-betweens for me! ;-) ;-)
Also, I wondered if my having an empty test directory was throwing it off
so I add a test file. I ran it twice in a row and it added the file twice.
Almost as if once it decides to rebuilds it re-adds everything. No
objections, just not was I understood from docs (since *I* didn't find it in
the docs) and mailing liat (DH) inputs --- jsut for the record...
regards
Adam
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
