ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 25003] New: - ejbjar documentation not complete
Date Wed, 26 Nov 2003 10:08:22 GMT
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=25003>.
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=25003

ejbjar documentation not complete

           Summary: ejbjar documentation not complete
           Product: Ant
           Version: 1.5.4
          Platform: All
               URL: http://ant.apache.org/manual/
        OS/Version: All
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Documentation
        AssignedTo: dev@ant.apache.org
        ReportedBy: mbrooks@rdfgroup.com


ejbjar task allows a property manifest, defining the location of a custom
manifest to be included in the ejb jar file produced. 
This works in exactly the same manner as the jar task - however the 
documentation does not reflect this.
I suggest that the relevent line from the jar documentation is copied into the
ejbjar documentation.

i.e.
manifest | the manifest file to use. This can be either the location of a
manifest, or the name of a jar added through a fileset. If its the name of an
added jar, the task expects the manifest to be in the jar at
META-INF/MANIFEST.MF | 	No

and maybe an example, for instance:

<ejbjar srcdir="${classes.dir}"   
descriptordir="${clas.deployment.descriptors.dir}"
basejarname="${base.jar.name}" 
dependency="none"  manifest="${deployment.descriptors.dir}/META-INF/MANIFEST.MF">

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org


Mime
View raw message