Return-Path: <matt@stargus.com>
Mailing-List: contact user-help@ant.apache.org; run by ezmlm
Delivered-To: mailing list user@ant.apache.org
Received: (qmail 99674 invoked from network); 13 Feb 2003 22:14:06 -0000
Received: from medusa.stargus.com (HELO xchange.stargus.com) (65.193.169.162)
  by daedalus.apache.org with SMTP; 13 Feb 2003 22:14:06 -0000
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: New Line in manifest
Date: Thu, 13 Feb 2003 17:14:10 -0500
Message-ID: <9093431B64301C47986EF078512912AD7B8170@xchange.stargus.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: New Line in manifest
Thread-Index: AcLTrOO/1yS1y8dHShK+pBX3w8NHYwAADHpg
From: "Matt Lyon" <matt@stargus.com>
To: "Ant Users List" <user@ant.apache.org>
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

Thanks for the workaround idea... I'm trying to remember my property =
inheritance rules... if I define them in the buildfile with default =
values, the values that are set in build.properties will still override, =
correct?

-----Original Message-----
From: Dominique Devienne [mailto:DDevienne@lgc.com]
Sent: Thursday, February 13, 2003 5:12 PM
To: 'Ant Users List'
Subject: RE: New Line in manifest


Prior to defining the <manifest>, assign short default values to all =
your
version properties (like <property name=3D"version.major" value=3D"M" =
/>,
etc...), and if some lazy developer (dixit) doesn't define then, then =
you'll
end up with M.m.r.b instead of:

${version.major}.${version.minor}.${version.revision}.${version.build}

It's of course just a turn around. --DD

-----Original Message-----
From: Matt Lyon [mailto:matt@stargus.com]=20
Sent: Thursday, February 13, 2003 4:02 PM
To: Ant-User (E-mail)
Subject: New Line in manifest

Hi,

I have an inline <manifest> parameter in my <jar> task that stamps my =
jars'
manifest files with
=3D${version.major}.${version.minor}.${version.revision}.${version.build}=

which are expanded from a build.properties file. The problem is that, if =
a
lazy developer does not define these values in the build.properties =
file,
the entry comes out as
Version=3D${version.major}.${version.minor}.${version.revision}.${version=
.buil
d}, and because the line is so long, it spills over to a new line... =
this
breaks the jar when it is deployed to WebLogic. Is there a workaround =
for
this to keep lengthy strings inserted into a manifest on one line only, =
or
is there a char limit for manifest entries defined by the jar spec that =
I am
not aware of?

Matt

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