proposal to uplevel JDNC project structure
As I hinted at in a separate thread, we'd like to propose a slight project restructuring to the java.net JDNC project.
We'd like to uplevel jdnc.dev.java.net so that it's more of an uber-project (aka "Swing Labs") which contains a myriad of subprojects which can be used either individually or together. Under this master project we would create an individual project for each of JDNC's 3 layers: Swing Extensions, JDNC Components, JDNC Markup. Each would have their own CVS module, forum, & mailing lists, but they would share the JCA/licensing. We would provide a site where all subprojects could be downloaded together as a convenience and possibly provide a site with integrated documentation (javadoc).
1. It would allow us to add additional subprojects in the spirit of exploring extensions to Swing which may not fit into JDNC's currently defined scope. Such projects would be easier for us to initiate because they could leverage the JDNC project infrastructure (e.g. JCA, license, lawyers, etc)
2. It makes it easier for the community to pick and choose their areas of interest without having to grok/download the entire thing. (e.g. it's clear many folks JUST want JDNC's Swing Extensions layer).
3. It would make it easier to evolve each subproject at its own pace.
4. It will help minimize dependencies and spaghetti-library syndrome.
- It would break existing cvs repositories
- It may have some API impact, although this should be minimal since we strove to keep the 3 layers clearly separated to begin with.
- It may require re-subscribing membership to subprojects, though perhaps by default we would transfer membership to at least the Swing Extensions project automatically.
We're curious what you think of this concept. If this causes more trouble than its worth then obviously we can keep the project structured as-is.