On Friday, February 8, 2002, at 01:15 PM, Scott Ellsworth wrote:
> /Users/work/Documents/coding/isis/source/products/first.jar,../products/second.
> jar
On further reading of the manual, I am presuming this is because neither
an unzip task nor a zipfileset in a zip task understand a comma
separated list of files as the source. From reading the archives,
though, this should be possible. Quoting Stefan Bodewig's post "Re:
Re[4]: Why are there paths and filesets?" on "2001-12-18"
> Anyway, you can convert a path to a fileset as long as you have a
> common root directory for your components.
In this case, I can require that all the jars I wish to glue together
live in ${build.productdir}, and can specify either the base names, or
the base names with paths in the property that I wish to have turn into
a fileset.
> It may be a little tricky, but you can use pathconvert to translate the
> path into a property that contains all components in a comma separated
> list.
I believe I have that with jar.zip="first.jar, second.jar"
> Using this property expanded as the value for a fileset's includes
> attribute should do the trick (it is Diane's, I just remembered it 8-).
It appears that the includes section used by a zipfileset is for files
inside a single zip, not a list of zip files. Similarly, it appears
that one gets to specify just one zip file in the unzip task.
As another way of tackling the problem, the Pathconvert task looks like
it can turn **/*.java into a comma separated list. Is there an
equivalent that will turn a comma separated list into a set of
pathelements suitable for sending to the jar task?
Scott
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
