http://nagoya.apache.org/bugzilla/show_bug.cgi?id=980
*** shadow/980 Wed Mar 14 17:23:37 2001 --- shadow/980.tmp.14657 Wed Mar 14 17:23:37 2001 *************** *** 0 **** --- 1,25 ---- + +============================================================================+ + | EjbJar should allow for a manifest file to be specified | + +----------------------------------------------------------------------------+ + | Bug #: 980 Product: Ant | + | Status: NEW Version: 1.3 | + | Resolution: Platform: PC | + | Severity: Enhancement OS/Version: Windows NT/2K | + | Priority: Component: Optional Tasks | + +----------------------------------------------------------------------------+ + | Assigned To: [EMAIL PROTECTED] | + | Reported By: [EMAIL PROTECTED] | + | CC list: Cc: | + +----------------------------------------------------------------------------+ + | URL: | + +============================================================================+ + | DESCRIPTION | + EJBs use the Class-Path: entry in the manifest file to search for classes that + are missing. This is especially useful when the EJB will be linked in with an + EAR file, as it can refer to library classes or other EJBS within the EAR file. + + In addition, according to the J2EE spec, all J2EE components should support + this, and so should the development tools. + + Because of this, EjbJar should have a way of specifying the manifest file to + use (with a default being the default manifest file currently used).
