From 9157b7607750a4b9f14cd1f047c9558546470d07 Mon Sep 17 00:00:00 2001
From: Jan Materne
The whenmanifestonly
parameter controls what happens when no
+
The whenmanifestonly
parameter controls what happens when no
files, apart from the manifest file, match.
If skip
, the JAR is not created and a warning is issued.
If fail
, the JAR is not created and the build is halted with an error.
-If create
, (default) an empty JAR file (only containing a manifest)
+If create
, (default) an empty JAR file (only containing a manifest)
is created.
(The Jar task is a shortcut for specifying the manifest file of a JAR file. @@ -230,9 +230,9 @@ If both an inline manifest and an external file are both specified, the manifests are merged.
-When using inline manifests, the Jar task will check whether the manifest -contents have changed (i.e. the manifest as specified is different in any way -from the manifest that exists in the Jar, if it exists. +
When using inline manifests, the Jar task will check whether the manifest +contents have changed (i.e. the manifest as specified is different in any way +from the manifest that exists in the Jar, if it exists. If the manifest values have changed the jar will be updated or rebuilt, as appropriate.
@@ -314,9 +314,9 @@ produced by the above would look like this:Manifest-Version: 1.0
Built-By: conor
-Created-By: Apache Ant 1.5alpha
+Created-By: Apache Ant 1.6.5
-Name: common/class1.class
+Name: common/MyClass.class
Sealed: false