manifest.mf

I tried adding manifest.file=${src.dir}/manifest.mf to project.properties, but looking through the build-impl.xml I see that the manifest.available is usually accompanied by main.class condition, so it makes me believe that my manifest would be added only if the package has a main class, which mine, being a library, does not have. No matter what I tried, the resulting library jar contains just the auto-generated manifest with only Ant-Version and Created-By. Remus Rusanu I ended up adding a Jar task in the build.xml, which was really good since it allowed me to add a Sign task also after the

Adding custom key-value-pairs to the MANIFEST.MF using Build.scala seems not to work. Here is my code: import sbt._ import Keys._ import java.util.Date object Build extends Build { packageOptions in (Compile, packageBin) += Package.ManifestAttributes( "Build" -> "true" ) } When I add: packageOptions in (Compile, packageBin) += Package.ManifestAttributes( "Sign" -> "true" ) To my build.sbt then only Sign reaches my MANIFEST.MF. Any thoughts? I think you may want something like this (note the manifestSettings added to the settings of the project). import sbt._ import Keys._ import java.util.Date

Are there any conventions for the MANIFEST.MF file in a Java JAR beyond the JAR specification ? Interesting information I might want to include are: Build date and other build information, SVN Revision, perhaps a description. I haven't found suggestions how to name the corresponding keys. Are there any de facto standards or at least common key names that are used in manifests for things that are not covered by the spec? The JAR Manifest: Overview mentions that "Attributes which are not understood are ignored." Anything but a Main Attribute should be OK. Here's a somewhat more comprehensive

This is a really silly question that I can't fine a difinitive answer to. Background. I'm using Eclipse (with one of the ANT plugins, on an XP terminal). I have just started playing with ANT, in the [jar] directive I am setting the location of my finished JAR file and I get the following when I 'unzip' the file META-INF/MANIFEST.MF MyMainFile.class which is consistent with that found on the oracle web site for the internal structure. (here http://docs.oracle.com/javase/tutorial/deployment/jar/view.html ) But when I try to run my file I get a 'main class not found' error ? I have seen some

To run maven-shade-plugin, I have to use to method described here due to signed dependencies, as shown here: <plugin> <artifactId>maven-shade-plugin</artifactId> <executions> <execution> <phase>package</phase> <goals><goal>shade</goal></goals> <configuration> <filters> <filter> <!-- filter out signature files from signed dependencies, else repackaging fails with security ex --> <artifact>*:*</artifact> <excludes> <exclude>META-INF/*.SF</exclude> <exclude>META-INF/*.DSA</exclude> <exclude>META-INF/*.RSA</exclude> </excludes> </filter> </filters> </configuration> </execution> </executions> <