Oops. I meant Rob, of course.
On 18/06/2013 4:34 PM, Bruce Atherton wrote:
You are right that it is inefficient, but it is easy to understand. If
you want to get efficient, you could create the main.jar with
inclusions of [1] using the src attribute for the other jars.
As for the manifest, wh
You are right that it is inefficient, but it is easy to understand. If
you want to get efficient, you could create the main.jar with inclusions
of [1] using the src attribute for the other jars.
As for the manifest, while this would be tricky for a general purpose
jar merging tool, it isn't a
Rob,
There are various open source solutions out there to do what you're
looking for, but there is no "built-in" way to do what you want to do
using plain Java. I saw someone else suggest one-jar which is what I
would have suggested, too. There is another one called Meta Jar that
basically
On Tue, Jun 18, 2013 at 11:54 AM, Bruce Atherton wrote:
> It is fairly trivial to do. In your main jar target:
>
> 1. create a temporary directory
> 2. run the unjar task
> 3. jar up your main jar, including the contents of the temporary
> directory
> 4. delete the temporary directo
It is fairly trivial to do. In your main jar target:
1. create a temporary directory
2. run the unjar task
3. jar up your main jar, including the contents of the temporary
directory
4. delete the temporary directory
See http://ant.apache.org/manual/Tasks/unzip.html for docs on
Thanks Peter. I did it with a replaceregex task now.
On Wed, Jun 12, 2013 at 2:55 AM, Peter West wrote:
> Hello Michael,
>
> As far as I know, you can't edit arbitrary files with the propertyfile
> task. The files have to be valid Java property files. For the restrictions
> on property files, s
In that case, is there an ant task that will enable me to explode the jar file
and add the classes that way. I could simply explode the jars in my
development hierarchy in Eclipse, but I would rather leave them untouched there
and only explode them when I build the main jar file. I looked in t
