Doug Bateman a écrit : > Howdy all, > > Tonight while browsing through the latest commons projects, it > occurred to me the once modest commons project has grown substantially > over time and has a lot of great stuff. There are now lots of sub > projects. Actually, it's 37 active subprojects to be exact. Plus the > archived projects. And the release numbering, JRE requirements, and > dependency graph can get a bit confusing. (Took me several hours to > map it out.) > > So I started thinking about what really makes it important to separate > projects: > + Different large external dependencies you wish to keep separate. > + Projects that aren't related. > + Projects that have very different user communities (e.g. > commons-math versus commons-dbcp).
Raising one question: do you thing some production project could use latest version of project commons.A and old version of commons.B ? They would probably not like merging both projects into one. Is this a use case we want to adress or is it too theoretical ? Luc > > And on the flip side, the benefits that come from having one artifact > and one release number to track, instead of a whole heap of release > numbers and dependencies to manage. > > Then it hit me... most of the dependencies are with other commons > projects, and on Java itself. And quite a few of the projects run on > the same version of Java. Could this network of interrelated projects > be simplified by consolidating a handful of projects together as a > single project? > > If so, what are the tradeoffs and what might it look like. > > So that's the question... would it potentially be beneficial to > consolidate some of the projects? What do we lose? What do we gain? > > To help get discussion and thoughts flowing, I've attached some notes > to the bottom of this email (and in attached txt files). Please don't > interpret these considerations as an actual final proposal... I'm > including them simply as a basis to initiate a possible discussion. > > Regards, > Doug --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
