Leo Simons wrote:
I personally think that it is a good idea to seperate out non-J2SE-specific
non-Harmony-specific stuff as much as possible. I also think it is a good idea
to evaluate very carefully on a case-by-case basis whether it makes sense to
have that kind of code live under the "harmony" banner -- experience has shown
that breaking out "true" utility stuff can help result in wider usage of that
stuff which tends to result in more bugfixes, better code, etc.
Certainly something to consider. Only issue is one of necessary control
- we need to have a set of behaviors driven by spec/tck reasons that a
general purpose package wouldn't care about.
For example (and I'm being really naive here) I can imagine that java.util
could be built on top of jakarta-commons-collections, or that java.util.logging
could be built on top of log4j (now that'd be cool).
Well, Commons Collections depends on java.util :)
But this is just me imagining stuff that might be possible in the future. For
now it doesn't make sense to worry or think about this too much - we'll see
what kind of ties between harmony and something like jakarta-commons (or
whatever other part of the open source java space we're on about here) is
possible as the issue comes up.
Yep..
cheers!
Leo
