On Friday 18 July 2003 11:03, Stefan Gybas wrote:
Jan Schulz wrote:
I've also come to the conclusion that adding the version number to JARs
in /usr/share/java/ is a bad idea. Take for example libxercres2-java: If
you've used /usr/share/java/xercesImpl-2.3.0.jar in another package and
then
E.L. Willighagen (Egon) wrote:
Since Xerces tends to give a lot of trouble moving from one version to
another, even within the 2.x series!, a more granular packaging would
be nice... i.e. separate packages for 2.3 and 2.4, etc...
Probably yes. But I don't have the time to maintain that many
BTW, I've not seen any package that usees the versioned JAR - so
it obviously is not useful.
This is not a valid argument. Just because debian packages don't use a
feature doesn't mean users aren't using the feature with their own
home-grown software.
Ben. :)
--
To UNSUBSCRIBE, email to
From: Stefan Gybas [EMAIL PROTECTED]
Subject: junit-freenet, was Re: Bug#165504 acknowledged by developer
Date: Tue, 15 Jul 2003 20:23:30 +0200
Package: junit
Section: contrib/devel
Version: 3.8.1-3
Depends: kaffe | java-virtual-machine
So it does not depend on any packages outside of main.
On Saturday 19 July 2003 01:23, Takashi Okamoto wrote:
From: Stefan Gybas [EMAIL PROTECTED]
Subject: junit-freenet, was Re: Bug#165504 acknowledged by developer
Date: Tue, 15 Jul 2003 20:23:30 +0200
So it does not depend on any packages outside of main. It is in contrib
because it does
Hallo E.L.,
* E.L. Willighagen (Egon) wrote:
you considered a SWT drop in? Ah, no, just checked libswt-java is in contrib
too... so, that won't help...
I haven't tested swt with kaffe, but I think that it should work. The
problem is, that it is build from eclipse source and if that runs under
Hi,
On Fri, 2003-07-18 at 20:42, Jan Schulz wrote:
I haven't tested swt with kaffe, but I think that it should work. The
problem is, that it is build from eclipse source and if that runs under
kaffe is something to be investigated :( Anyway it also has motif portions,
so...
Helmer Krämer
Hallo Mark,
* Mark Wielaard wrote:
Helmer Krämer recently fixed some things in Kaffe to get Eclipse to
startup (doesn't do much more then startup, but it is a start):
http://www.kaffe.org/pipermail/kaffe/2003-July/043015.html
And Eclipse of course runs with gcj:
http://klomp.org/mark/gij_eclipse/
Hallo Philipp,
* Philipp Meier wrote:
On Fri, Jul 18, 2003 at 08:42:06PM +0200, Jan Schulz wrote:
kaffe is something to be investigated :( Anyway it also has motif portions,
so...
Can't then be the gtk binding of swt be of use?
In the moment (not yet in unstable, but I hope soon:
Hallo Stefan,
* Stefan Gybas wrote:
Ben Burton wrote:
This is not a valid argument. Just because debian packages don't use a
feature doesn't mean users aren't using the feature with their own
home-grown software.
But I think the process should go in the other direction: Instead of
specifing
Hallo Stefan,
* Stefan Gybas wrote:
(e.g. to use a well-defined class path)
BTW: I just had some problems with that:
SWT is (2.1.1-3) now avavilable with motif and gtk bindings. The
problem is, that gtk is distributet in two jars and motif in one jar
(license issues...). So when someone
But I think the process should go in the other direction: Instead of
specifing something and waiting for people to implement it we should
document what has been implemented and is working well.
This is not necessarily true; take as an example the /usr/lib/jni
proposal. Although pretty much
On Friday 18 July 2003 11:03, Stefan Gybas wrote:
Jan Schulz wrote:
I've also come to the conclusion that adding the version number to JARs
in /usr/share/java/ is a bad idea. Take for example libxercres2-java: If
you've used /usr/share/java/xercesImpl-2.3.0.jar in another package and
then
Hello
Thanks for taking over java-common. I thought you would. :)
On Fri, Jul 18, 2003 at 11:03:22AM +0200, Stefan Gybas wrote:
Jan Schulz wrote:
I just wanted to know what direction. I'm not suggesting to discuss
the things word by word...
I've collected some suggestions for building
Ben Burton wrote:
This is not a valid argument. Just because debian packages don't use a
feature doesn't mean users aren't using the feature with their own
home-grown software.
But I think the process should go in the other direction: Instead of
specifing something and waiting for people to
Hallo E.L.,
* E.L. Willighagen (Egon) wrote:
you considered a SWT drop in? Ah, no, just checked libswt-java is in contrib
too... so, that won't help...
I haven't tested swt with kaffe, but I think that it should work. The
problem is, that it is build from eclipse source and if that runs under
Hi,
On Fri, 2003-07-18 at 20:42, Jan Schulz wrote:
I haven't tested swt with kaffe, but I think that it should work. The
problem is, that it is build from eclipse source and if that runs under
kaffe is something to be investigated :( Anyway it also has motif portions,
so...
Helmer Krämer
Hallo Mark,
* Mark Wielaard wrote:
Helmer Krämer recently fixed some things in Kaffe to get Eclipse to
startup (doesn't do much more then startup, but it is a start):
http://www.kaffe.org/pipermail/kaffe/2003-July/043015.html
And Eclipse of course runs with gcj:
http://klomp.org/mark/gij_eclipse/
Hallo Stefan,
* Stefan Gybas wrote:
(e.g. to use a well-defined class path)
BTW: I just had some problems with that:
SWT is (2.1.1-3) now avavilable with motif and gtk bindings. The
problem is, that gtk is distributet in two jars and motif in one jar
(license issues...). So when someone
But I think the process should go in the other direction: Instead of
specifing something and waiting for people to implement it we should
document what has been implemented and is working well.
This is not necessarily true; take as an example the /usr/lib/jni
proposal. Although pretty much
20 matches
Mail list logo
