ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From pedro surf <>
Subject Changing manifest task to accept classpath by reference and nested element!
Date Thu, 12 Feb 2009 13:53:15 GMT
Hi everybody,
this is my first e-mail do this list. Recently I had to create a jar file
with a classpath in the manifest file. The classpath of my project was
defined as a nested element but the manifest task only accept it as a value
in the attribute element. I had to use a manifestclasspath task to convert
the classpath to a property and then use its value.

I believe changing the manifest task to accept a classpathref as a parameter
or a nested element would be a great change that would increase the
readability of the build and reduce the amount of code necessary to do a
simple (and usual) task.

I don´t know if this change is already in the plans of the ant team, but if
not I would like to do it. However I´ve never worked in a open source
project, so any help (best practices, code reviews, ...) would be great.


  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message