C
Cameron McCormack
Hi.
I'm confused as to the difference between the Package-* and
Implementation-* manifest attributes mentioned in [1]. Could someone
please explain when I would use one and when the other?
Also, is there a preferred way to give a title to a whole JAR file in
the manifest, rather than names for the packages within? For example, I
want to have a batik-all.jar file, which includes all of Batik's classes
plus some dependencies (e.g. org.w3c.dom.svg.* classes), and other
individual JAR files (like batik-dom.jar, batik-swing.jar, ...) which
each have (separable) parts of Batik. If I put an
Implementation-Title: Batik all-in-one JAR
in the main section of batik-all.jar's manifest, then that seems to
actually name the packages within the JAR, rather than the JAR itself.
Is that correct?
Thanks,
Cameron
[1]
http://java.sun.com/j2se/1.5.0/docs/guide/versioning/spec/versioning2.html
I'm confused as to the difference between the Package-* and
Implementation-* manifest attributes mentioned in [1]. Could someone
please explain when I would use one and when the other?
Also, is there a preferred way to give a title to a whole JAR file in
the manifest, rather than names for the packages within? For example, I
want to have a batik-all.jar file, which includes all of Batik's classes
plus some dependencies (e.g. org.w3c.dom.svg.* classes), and other
individual JAR files (like batik-dom.jar, batik-swing.jar, ...) which
each have (separable) parts of Batik. If I put an
Implementation-Title: Batik all-in-one JAR
in the main section of batik-all.jar's manifest, then that seems to
actually name the packages within the JAR, rather than the JAR itself.
Is that correct?
Thanks,
Cameron
[1]
http://java.sun.com/j2se/1.5.0/docs/guide/versioning/spec/versioning2.html