ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Conor MacNeill <co...@cortexebusiness.com.au>
Subject Re: ejbjar not adding manifest properly
Date Thu, 17 Apr 2003 15:21:05 GMT
On Fri, 18 Apr 2003 12:00 am, Doyle, Jim wrote:
>
> 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)
>

No, it has nothing to do with these changes. The bulk of these changes affect 
the jar and manifest tasks which use Ant's Manifest class. The ejbjar task, 
on the other hand, since it already requires JDK 1.2+, uses the JDK Manifest 
class, which has slightly different behaviour (and bugs). See, for instance, 
this bug report

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18206

If you follow the spec link in that bug report you will note that a valid 
manifest MUST have a Manifest-Version header. I'm not sure if the JDK's 
manifest class is requiring that field but you should have it in your 
manifests. You also need to be careful to end your manifest with new lines.

Conor

-- 
Conor MacNeill
Blog: http://codefeed.com/blog/


Mime
View raw message