Hi Ralf,
Creating different JAR contents than upstream only leads to user
irritation. Disk space is relativly cheap today so that should not be an
issue.
I also think that disk space is not the main issue. When I asked my
question I was more thinking about maintainability (jars with the same
On Mon, Jun 30, 2008 at 07:04:00PM +0200, RalfGesellensetter wrote:
> Am Montag 30 Juni 2008 schrieb Florian Grandel:
> > Thank you very much for your opinion. That's what I was thinking as
> > well and how I started doing it now.
>
> Hi Florian, hi Michael,
>
> sounds sound to me - but:
> Inters
Am Montag 30 Juni 2008 schrieb Florian Grandel:
> Thank you very much for your opinion. That's what I was thinking as
> well and how I started doing it now.
Hi Florian, hi Michael,
sounds sound to me - but:
Intersection also implies waste of space. In cases where the overlapping
base classes ext
Hi Matthew,
Matthew Johnson schrieb:
Ah, hmm, I think it only looks in /usr/share/java, since this was a tool
for Debian, and thats where all our jars are stored.
I forgot to mention that I modified your script to look into "my"
directory. This is a very simple modification and makes your scr
Hi Matthew,
Matthew Johnson schrieb:
It's unclear to me what they want to be configured at runtime by
changing the classpath.
I'll ask them and report back.
Wrapper scripts without classpath manifest items also result in
large classpaths containing items you shouldn't have to know about (you
On Mon Jun 30 10:01, Florian Grandel wrote:
> Hi Java developers,
>
>> One problem that I haven't solved so far is how to get the classpath
>> into the MANIFEST file as was proposed earlier in this thread.
>
> As you may have remarked from my earlier posts I am working with the
> JPackage guys rec
Hi Java developers,
One problem that I haven't solved so far is how to get the classpath
into the MANIFEST file as was proposed earlier in this thread.
As you may have remarked from my earlier posts I am working with the
JPackage guys recently. Their "recommendation to Java developers"
argum
Hi Michael,
Michael Koch schrieb:
I would do it as upstream does it. This doesnt confuse users as that is
what they know from upstream. We had enough problems when our jars were
too mich different from upstream in the past.
Thank you very much for your opinion. That's what I was thinking as we
On Sun Jun 29 23:25, Richard Cole wrote:
>
> I'd be pleased if you (the collective of debian java packagers) would
> look over what I've done and provide comments, hints and suggestions.
Well, some general observations just looking at the packaging. There is
a built jar in the source, which isn't
9 matches
Mail list logo
