On Monday, September 15, 2003 at 08:42:40 (-0400) Howard M. Lewis Ship writes: >... >I have HiveMind building locally using Maven 1.0-rc-1 (out of Maven's >CVS). I'm going to look into refactoring the code base so that there >are multiple sub-projects. Initially, I envision a framework >subproject (for the framework and the core services ... which is to >say, what's currently in CVS). Additionally, we should add a "standard >library" module, for useful stuff that doesn't absolutely have to be >in the framework propery and, perhaps, a sandbox module library, for >new code under less stringent release mechanisms. > >I this a good vision? Or should the other modules become new commons >sandbox projects unto themselves ... or be elsewhere, such as on >SourceForge?
I think a hierarchy is fine. If you can't use the other modules without the main module, perhaps making them separate sandbox projects is not terribly useful. On the other hand, perhaps the main module could be just another "mix-in" that you check out from the repository to add to separate projects to support them. Or maybe I'm missing the point entirely. This is one area I have struggled with many times before. Maven has some promise, as you have noted, to allow support for clean separation of modules. I tried doing this entirely in CVS, but was not altogether successful. >What kind of services can we create for the additional libraries? Would a data access service be too ambitious? Even something that helps with ordinary JDBC setup and testing would be nice/useful for many projects. Bill --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
