Hi Stefan,
Stefan Gybas wrote:
IIRC lib-sax-java only contained the SAX 1 interface classes. So if
you want the SAX API in a seperate package you should support SAX
version 2 (which is compatible with version 1).
As I've already told, I'm planning to split xml-apis.jar (which is
On Tue, Oct 01, 2002 at 01:20:09PM +0200, Xavier Renard wrote:
What about xerces in this case? It already provides DOM,SAX,JAXP but not
Trax which comes with xml-apis.jar apparently.
That's true but I don't see a problem with this. Even if both JARs are
in the class path everything should
On Mon, Sep 30, 2002 at 10:25:05AM -0700, Stephen Zander wrote:
[Ant, Xalan2]
Do these classes work with gjc/kaffe?
I've done some tests with Ant and at least the core classes (i.e.
the ones in ant.jar) worked fine. Most of the optional classes in
ant-optional.jar do not, so I was thinking
On Tuesday 01 October 2002 13:45, Stefan Gybas wrote:
On Mon, Sep 30, 2002 at 10:25:05AM -0700, Stephen Zander wrote:
[Ant, Xalan2]
Do these classes work with gjc/kaffe?
I've done some tests with Ant and at least the core classes (i.e.
the ones in ant.jar) worked fine. Most of the
On Tue, Oct 01, 2002 at 02:01:56PM +0200, E.L. Willighagen wrote:
What about splitting those libs into lib*-java and lib*-doc ? The former
would then go into main, and the doc into contrib?
Yes, that would be the way to go if there's no free javadoc but this means
additional work for the
On Tue, Oct 01, 2002 at 02:07:05PM +0200, Stefan Gybas wrote:
On Tue, Oct 01, 2002 at 02:01:56PM +0200, E.L. Willighagen wrote:
What about splitting those libs into lib*-java and lib*-doc ? The former
would then go into main, and the doc into contrib?
Yes, that would be the way to go if
Hi
This was a interesting note. I'll CC the debian-java@lists.debian.org
list for discussion.
Regards,
// Ola
On Mon, Sep 30, 2002 at 09:59:26PM +0200, Torsten Knodt wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello,
most libraries have api docs created with javadocs. When
Hi Stefan,
Stefan Gybas wrote:
IIRC lib-sax-java only contained the SAX 1 interface classes. So if
you want the SAX API in a seperate package you should support SAX
version 2 (which is compatible with version 1).
As I've already told, I'm planning to split xml-apis.jar (which is
created by
On Tue, Oct 01, 2002 at 01:20:09PM +0200, Xavier Renard wrote:
What about xerces in this case? It already provides DOM,SAX,JAXP but not
Trax which comes with xml-apis.jar apparently.
That's true but I don't see a problem with this. Even if both JARs are
in the class path everything should
On Mon, Sep 30, 2002 at 10:25:05AM -0700, Stephen Zander wrote:
[Ant, Xalan2]
Do these classes work with gjc/kaffe?
I've done some tests with Ant and at least the core classes (i.e.
the ones in ant.jar) worked fine. Most of the optional classes in
ant-optional.jar do not, so I was thinking
On Tuesday 01 October 2002 13:45, Stefan Gybas wrote:
On Mon, Sep 30, 2002 at 10:25:05AM -0700, Stephen Zander wrote:
[Ant, Xalan2]
Do these classes work with gjc/kaffe?
I've done some tests with Ant and at least the core classes (i.e.
the ones in ant.jar) worked fine. Most of the optional
On Tue, Oct 01, 2002 at 02:01:56PM +0200, E.L. Willighagen wrote:
What about splitting those libs into lib*-java and lib*-doc ? The former
would then go into main, and the doc into contrib?
Yes, that would be the way to go if there's no free javadoc but this means
additional work for the
On Tue, Oct 01, 2002 at 02:07:05PM +0200, Stefan Gybas wrote:
On Tue, Oct 01, 2002 at 02:01:56PM +0200, E.L. Willighagen wrote:
What about splitting those libs into lib*-java and lib*-doc ? The former
would then go into main, and the doc into contrib?
Yes, that would be the way to go if
13 matches
Mail list logo