Mon, 25 Oct 2004 21:10:17 +0100,
Chris Burdess [EMAIL PROTECTED] wrote:
Dalibor Topic wrote:
I, too, want to see GNU JAXP integrated into GNU Classpath.
[...]
Moving GNU JAXP to the Classpath project is not a problem for the
current JAXP developers.
Note on modularisation: as I
Am Dienstag, 26. Oktober 2004 10:23 schrieb Arnaud Vandyck:
Mon, 25 Oct 2004 21:10:17 +0100,
Chris Burdess [EMAIL PROTECTED] wrote:
Dalibor Topic wrote:
I, too, want to see GNU JAXP integrated into GNU Classpath.
[...]
Moving GNU JAXP to the Classpath project is not a problem for the
Tue, 26 Oct 2004 10:39:12 +0200,
Michael Koch [EMAIL PROTECTED] wrote:
Am Dienstag, 26. Oktober 2004 10:23 schrieb Arnaud Vandyck:
[...]
Yes, other worst alternatives exist. Also, note that GNU JAXP
release cycle is not the same as classpath; and if we really want a
separate module, I
Hi there,
in an attempt to fix bug 10799 I saw that the affected class
(java.beans.PropertyEditorSupport) needs some general cleanup and fixing
(it was last modified in 1998!). I took the online version of the 1.5
API documentation and realized that the 2 constructors are now public
(were
Am Dienstag, 26. Oktober 2004 13:51 schrieb Robert Schuster:
Hi there,
in an attempt to fix bug 10799 I saw that the affected class
(java.beans.PropertyEditorSupport) needs some general cleanup and
fixing (it was last modified in 1998!). I took the online version
of the 1.5 API documentation
Robert Schuster wrote:
AFAIK the changes Sun made are binary compatible or am I wrong?
http://www.kaffe.org/~stuart/japi/jcompat.txt contains some notes I made
on exactly what kinds of changes are binary compatible. These are the
criteria that japitools use to determine what errors to list.
I
Michael == Michael Koch [EMAIL PROTECTED] writes:
Michael I would say go ahead but add @specnote tags telling what got
Michael changed in the public API.
Yes, I agree. Also the new methods should be marked @since 1.5.
Interesting, neither @specnote nor @since appear in hacking.texinfo.
Anybody
7 matches
Mail list logo