ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David T" <...@real.address.com>
Subject Ant Manifest Task Question: Class path within Manifests in EJB JAR and WAR files
Date Fri, 10 Dec 2004 04:41:52 GMT
Ant Manifest Task Question: Class path within Manifests in EJB JAR and
WAR
files

Is there a more elegant way of doing this:

<path id="deploy.lib.path">
    <fileset dir="${deploy.lib.dir}">
        <include name="*.*"/>
    </fileset>
</path>

<target name="aTarget"> 

	<!-- BAD PART START --->
	<pathconvert pathsep=" " property="deploy.lib.list"
refid="deploy.lib.path">
	    <map from="${deploy.lib.dir}/" to=""/>
	    <map from="${deploy.lib.dir}\" to=""/>			
	</pathconvert> 
	<!-- BAD PART END --->
	<!-- IDEALLY: I would like to a) get rid of this entirely and/or b)
move it out of the target -->

	<war 
	    <!-- details omitted -->
	    <manifest>
	        <attribute name="Class-Path" value="${deploy.lib.list}"/>
	    </manifest>                
	</war> 

</target>

If not has there been any talk about adding a class-path Nested element
to
the manifest task?
(already looked for other tasks that do this... Found nothing... )

Once upon a time (2002-02-01) some people (Robert Upshall, Ylan Segal,
Scott
Ellsworth) where discussing:
[...]
>     <manifest>
[...]
>         <class-path>
[...] bla bla FileSet bla bla 
>         </class-path>
>     </manifest>
[...]






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


Mime
View raw message