Hi Andrew,
On 3/10/2011 3:48 AM, Dr Andrew John Hughes wrote:
* Separating out the client (awt/swing/etc) code from the jdk repo into a
separate repo
Why would we want to do this? IME, there are lots of interdependencies with
the other code and
this would make the build a nightmare.
Not at all. AWT/Swing/2D have a lot of inter-dependencies with each
other, but no deep dependencies with other parts of JDK. I believe the
Sound libraries are very similar in this regard as well. Separating them
out makes a lot of sense to speed up the build time for those primarily
working on bugs and enhancements in these areas only.
What particular problems do you anticipate with their separation?
Hey, I'd just make it all one repository as they all interdepend on each other
One huge "all-in-all" repository is great for integrators, porters, or
maintainers, but it isn't that convenient for developers working on
specific areas of JDK. Primarily because of the unnecessarily increased
build time.
Since it's always possible to make a clone of the whole 'forest', and
hence get all the repos virtually at once, I don't really see any
problems with making some parts of the class (and native) libraries
separate repositories.
--
best regards,
Anthony
