ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Doyle, Jim" <jdo...@iso-ne.com>
Subject Re: ejbjar not adding manifest properly
Date Thu, 17 Apr 2003 14:00:49 GMT
Hi,

I have noticed the same Ant 1.5.3 problem as Ashoka in his ant-user posting
http://marc.theaimsgroup.com/?l=ant-user&m=104256242220940&w=2

If you pass a manifest to the ejbjar task
(<ejbjar manifest="my-manifest.txt"...>)
with only one line
(Class-Path: time-swing.jar)
it will come up empty in the generated EJB jar file.

If you pass a manifest with the Manifest-Version attribute
(Manifest-Version: 1.0
Class-Path: time-swing.jar)
this will appear in the generated EJB jar file correctly.

Maybe this has something to do with one of the below changes
to manifest handling between Ant 1.4 and 1.5?
(See
http://cvs.apache.org/viewcvs/ant/WHATSNEW?rev=1.400&content-type=text/vnd.v
iewcvs-markup)

* The Created-By header in the default manifest now contains the JVM
  vendor and version according to the jar specification. A new header,
  Ant-Version provides the Ant version used to create the jar.
* Merging of Manifests in jar now works as documented.
* <ejbjar> will add a manifest to the generated jar based on the naming
  convention in use. This overrides the manifest specified in the
  <ejbjar> attribute

This does not appear to be a big deal, but it would be good if the ejbjar
documentation mentioned the need for the Manifest-Version attribute.  And 
actually, the 1.5.3 manual doesn't document the ejbjar task's 
manifest attribute.  The manual describes a manifest attribute for ejbc,
but not for ejbjar.

Thanks,
Jim Doyle


Mime
View raw message