Return-Path: 
 <ant-user-return-14581-qmlist-jakarta-archive-ant-user=jakarta.apache.org@jakarta.apache.org>
Delivered-To: apmail-jakarta-ant-user-archive@apache.org
Received: (qmail 56028 invoked from network); 16 Nov 2001 12:04:16 -0000
Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131)
  by daedalus.apache.org with SMTP; 16 Nov 2001 12:04:16 -0000
Received: (qmail 5245 invoked by uid 97); 16 Nov 2001 12:04:06 -0000
Delivered-To: qmlist-jakarta-archive-ant-user@jakarta.apache.org
Received: (qmail 5208 invoked by uid 97); 16 Nov 2001 12:04:05 -0000
Mailing-List: contact ant-user-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:ant-user-unsubscribe@jakarta.apache.org>
List-Subscribe: <mailto:ant-user-subscribe@jakarta.apache.org>
List-Help: <mailto:ant-user-help@jakarta.apache.org>
List-Post: <mailto:ant-user@jakarta.apache.org>
List-Id: "Ant Users List" <ant-user.jakarta.apache.org>
Reply-To: "Ant Users List" <ant-user@jakarta.apache.org>
Delivered-To: mailing list ant-user@jakarta.apache.org
Received: (qmail 5197 invoked from network); 16 Nov 2001 12:04:05 -0000
X-Authentication-Warning: bodewig.bost.de: bodewig set sender to
 bodewig@bost.de using -f
To: ant-user@jakarta.apache.org
Subject: Re: Manifests, copy task
References: <6699556.1005910300062.JavaMail.root@127.0.0.1>
From: Stefan Bodewig <bodewig@apache.org>
Date: 16 Nov 2001 12:59:20 +0100
Message-ID: <m3d72jexk7.fsf@bodewig.bost.de>
Lines: 40
User-Agent: Gnus/5.0807 (Gnus v5.8.7) XEmacs/21.4 (Civil Service)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

On Fri, 16 Nov 2001, brian ewins <brian.ewins@btinternet.com> wrote:

> Also, is what Conor's saying right?

If Conor says, it is possible, it is 8-).  He has written the code.

> I have the 1.4 code in front of me and I can't see anything in the
> jar task or 'manifest' code that would allow this?

I only have the 1.5alpha code on my machine ATM, here <jar> supports a
nested <manifest> element, which in turn supports nested <section> and
<attribute> children.

<attribute> has name and value attributes - if you convert your <path>
to a <property> (using <property>'s refid attribute), you can get its
value into a Manifest file attribute via the value attribute and ${}
expansion of your property.

> On an unrelated note... does anyone else find it odd that the 'copy'
> task can add a fileset but not a path?

Just today somebody has asked the same question, but honestly, I've
never thought about using a path in copy before.  I think one of the
main problems is that <fileset> doesn't support absolute paths on
filesystems with multiple roots like Windows, otherwise you could get
away without duplication by something like

<path id="for.compiles">
  <fileset id="for.copy" dir="/">
    <include name="${some.jar}" />
    <include name="${some-other.jar}" />
  </fileset>
</path>

and use a reference to for.compiles in javac, rmic, javadoc whatever
and a reference to for.copy in copy, war or similar.

Main drawback, this won't work on non-Unix systems.

Stefan

--
To unsubscribe, e-mail:   <mailto:ant-user-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:ant-user-help@jakarta.apache.org>