Return-Path: Delivered-To: apmail-jakarta-ant-user-archive@jakarta.apache.org Received: (qmail 22675 invoked by uid 500); 10 Aug 2001 23:13:34 -0000 Mailing-List: contact ant-user-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: Reply-To: ant-user@jakarta.apache.org Delivered-To: mailing list ant-user@jakarta.apache.org Received: (qmail 22662 invoked from network); 10 Aug 2001 23:13:34 -0000 Message-ID: <007801c121f2$f527e800$3de0223f@cognetnt> From: "Conor MacNeill" To: References: <81A3EB2A9C7BD411AAE800D0B75FB1BE265DAC@devexch01.oakscape> Subject: Re: Modifying manifest files for EJB jars Date: Sat, 11 Aug 2001 09:15:20 +1000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N Brian, Yes, I think that will be possible. I have recently added that capability to the task. The next step will be to pull some of the code out into some sort of jar service in the Ant core and then connect ejbjar up to that. Conor ----- Original Message ----- From: "Leon, Brian" To: Sent: Saturday, August 11, 2001 5:06 AM Subject: Modifying manifest files for EJB jars > Would it be possible for a future release on the task to pass > strings of text that could be incorporated into the manifest file as header > items for each EJB jar file as it is compiled and jarred? > > e.g. > > > ... > > > Brian > >