>>> "Aaron M. Renn" <[EMAIL PROTECTED]> 16-Apr-00 8:55:45 PM >>>
Tom Tromey ([EMAIL PROTECTED]) wrote:
> Nic> What do the Classpath folks think of setting up a subversions
> Nic> module called:
> Nic> javax
> Nic> where we put the code for javax stuff that it outside the
Classpath
> Nic> project.
>
> Why not put it in Classpath? I'm all for that.
Aaron wrote:
>I have no objections to this.
I'm not sure it makes sense... but perhaps it doesn't matter.
Here's my reasons for think it should be seperate:
1. if it's in Classpath then it increases the Classpath development
2. every extension (except the core stuff like Swing) is outside of
the core Java libraries, which is Classpath's goal
3. we would need to keep the distributions seperate anyway (because
people who download Classpath don't necessarily want to download
servlet or mail)
4. each package (servlet, mail, etc..) would need seperate pages and
doc
I think 3 and 4 are probably the most significant but also probably
the most solvable.
Here's my suggestions for solving them:
- Classpath set up another CVS module for each javax package (as and
when they come along)
- Classpath link those CVS modules into the Classpath module (if they
want to)
- I set up seperate documentation as previously discussed.
Where is the Classpath CVS? Is it on subversions?
Nic
