Re: javax.naming work (Classpath vs ClasspathX)

[Nic Ferrier <nferrier at tf1 dot tapsellferrier dot co dot uk>]

>>>>> "Mark" == Mark Wielaard <mark@klomp.org> writes:

Mark> Actually the distinction is not about java.* vs javax.*. The GNU
Mark> Classpath project was setup to give us a set of free standard
Mark> java library classes.  So in principle all standards defined by
Mark> what Sun calls J2SE (Java 2 Standard Edition) will become part
Mark> of Classpath (some day). Whatever package they are in.


Actually I disagree with this.

I think Classpath should exist to do the core language classes. 

GNU projects should not become slaves to Sun marketing strategy
because that's all that decides what classes go into what
distribution.

There is a clearly logical separation between java.* and
javax.*. Classpath should do java.* and a few javax.* things (like
swing, because it's so machine specific) and ClasspathX should do all
other extension implementations.


Nic Ferrier