DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9431>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9431 Add an option to merge Manifest information in 'ejbjar' task [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |INVALID ------- Additional Comments From [EMAIL PROTECTED] 2002-05-31 01:56 ------- The <ejbjar> task supports adding two methods of adding manifests to the generated jars. 1. <ejbjar> will automatically pickup manifest files which are associated with the deployment descriptors <ejbjar> is processing. The association will depend on the naming scheme you are using. If you are using descriptor naming, eg your descriptor is Bean-ejb-jar.xml, the manifest will be Bean-manifest.mf. For the other naming schemes, where the desciptor has the vanilla name ejb-jar.xml, the manifest will be named manifest.mf. In all cases the manifest file should be colocated with the desriptor 2. You can specify a manifest attribute in the <ejbjar> task itself identifiying a file to be used as the manifest for all generated jars. Where both methods are used the first takes precedence. The effect of specifying these manifests is to add the manifest to the generic jar which is subsequently fed into the vendor specific tool (ejbc in weblogic's case). I'm pretty sure that earlier versions of ejbc did not propagate this manifest into the generated output jar. I'd suggest trying out the next beta (1.5 Beta2) And finally, just to clear up a misconception, <ejbjar> is not strictly considered an extension of <jar>. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
