ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dominique Devienne <DDevie...@lgc.com>
Subject RE: New Line in manifest
Date Thu, 13 Feb 2003 22:17:23 GMT
Depends who defines them first. That's why I said to define them just before
their use in <manifest>. That way, they're necessarily the last one set,
which is what you want. --DD

-----Original Message-----
From: Matt Lyon [mailto:matt@stargus.com] 
Sent: Thursday, February 13, 2003 4:14 PM
To: Ant Users List
Subject: RE: New Line in manifest

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="version.major" value="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] 
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
=${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=${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


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

Mime
View raw message