Return-Path: 
 <dev-return-53207-apmail-ant-dev-archive=ant.apache.org@ant.apache.org>
Delivered-To: apmail-ant-dev-archive@www.apache.org
Received: (qmail 48763 invoked from network); 26 Nov 2003 10:08:30 -0000
Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12)
  by minotaur-2.apache.org with SMTP; 26 Nov 2003 10:08:30 -0000
Received: (qmail 89594 invoked by uid 500); 26 Nov 2003 10:08:02 -0000
Delivered-To: apmail-ant-dev-archive@ant.apache.org
Received: (qmail 89559 invoked by uid 500); 26 Nov 2003 10:08:02 -0000
Mailing-List: contact dev-help@ant.apache.org; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:dev-unsubscribe@ant.apache.org>
List-Subscribe: <mailto:dev-subscribe@ant.apache.org>
List-Help: <mailto:dev-help@ant.apache.org>
List-Post: <mailto:dev@ant.apache.org>
List-Id: "Ant Developers List" <dev.ant.apache.org>
Reply-To: "Ant Developers List" <dev@ant.apache.org>
Delivered-To: mailing list dev@ant.apache.org
Received: (qmail 89546 invoked from network); 26 Nov 2003 10:08:02 -0000
Received: from unknown (HELO exchange.sun.com) (192.18.33.10)
  by daedalus.apache.org with SMTP; 26 Nov 2003 10:08:02 -0000
Received: (qmail 3409 invoked by uid 50); 26 Nov 2003 10:08:22 -0000
Date: 26 Nov 2003 10:08:22 -0000
Message-ID: <20031126100822.3408.qmail@nagoya.betaversion.org>
From: bugzilla@apache.org
To: dev@ant.apache.org
Cc: 
Subject: DO NOT REPLY [Bug 25003] New:  -
    ejbjar documentation not complete
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N
X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N

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