GNU bug report logs - #9088
Better java support with new JARS primary

Previous Next

Full log

Message #26 received at 9088 <at> debbugs.gnu.org (full text, mbox):

From: Jack Kelly <jack <at> jackkelly.name>
To: Ralf Wildenhues <Ralf.Wildenhues <at> gmx.de>
Cc: tsuna <tsunanet <at> gmail.com>, 9088 <at> debbugs.gnu.org, automake <at> gnu.org
Subject: Re: bug#9088: Java support
Date: Mon, 18 Jul 2011 17:33:58 +1000

On Mon, Jul 18, 2011 at 4:17 PM, Ralf Wildenhues <Ralf.Wildenhues <at> gmx.de> wrote:
> * Jack Kelly wrote on Sat, Jul 16, 2011 at 06:13:58AM CEST:
>> On Sat, Jul 16, 2011 at 9:55 AM, tsuna wrote:
>> > On Fri, Jul 15, 2011 at 1:58 AM, Stefano Lattarini wrote:
>> >> As my java foo is pretty weak, I'm not sure how to handle jar manifests,
>> >> jar entry points, or other jar/javac subtleties and advanced features.
>> >> Suggestions welcome.
>> >
>> > You can create the manifest manually fairly easily.  Here's an example
>> > in the project I'm in the process of autotoolizing:
>> > https://github.com/stumbleupon/opentsdb/blob/6059488f38fc8a51d426d6972eee6fdd1033d851/Makefile#L207
>>
>> Perhaps there should be support for a foo_jar_JARADD, that by analogy
>> to _LDADD, that specifies additional files to be included in the jar?
>
> Why would it have to be a new primary, instead of just reusing _LDADD?

Because, IMO, it's conceptually different. The output's being
assembled with `jar', not `ld'.

-- Jack

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.