The following snippet works on windows: <jar destfile="${deploy.file}" basedir="${tmpdir}/deploy" update="true" manifest="${tmpdir}/META-INF/MANIFEST.MF"> <metainf dir="${tmpdir}/deploy/${config}"> <patternset refid="deploy.config.path"/> </metainf> </jar> However, on Solaris it fails to update the jar file at all. If I remove the manifest attribute to the jar task, then it runs on Solaris. Unfortunately the default manifest is created and stuck in the jar.
Do you create your manifest (tmpdir hints, you would). If so, is it possible that it is newer than ${deploy.file}? If so again, this report is a duplicate of Bug 10755.
I do create my own manifest. I tried creating the manifest both before the jar file is copied (thereby the manifest being older then the jar) and creating it after the jar is copied (where the manifest would be new then the jar). Neither worked. In addition, the behavior is correct on windows 2000 and XP, 10755 seems to be a generic problem not platform specific.
OK, another try. Bug 12440? Could you please give the lastest build from <http://cvs.apache.org/~bodewig/gump/ant1.5.2alpha/> a try and see whether the problem is fixed with that?
Does the problem still exist with Ant 1.5.3beta?
We no longer build on Solaris. I think I included the build script - maybe you can try.