Hi, Here are a few more thoughts about the encapsulation ... I think that the goal should be to allow a project to take care of itself if it wishes but to easily work with a third party to produce distributions and documentation if desired.
Right now there are server definitions and repository definitions. If these were absored at the project level, which is what I'm doing with the maven descriptors, then a project can take care of itself but additionally small projects that don't have the resources to do things like nightly builds can punt this off to third party like Gump. Define things at the project level, completely encapsulate the information and I believe you will have a more sound design because it gives the autonomy and freedom to do what they like but it also allows cooperation. I think it would make more sense to define everything in terms of projects and place information like the cvs module with that. Which is backward from the current model. I think this encapsulation will get you a lot further in bringing more projects on board with a lot less work. Right any of the Maven projects can publish themselves and produce nightlies but this could easily be done by a tool like Gump. At this point in time I think Maven has a better model that will encourage more cooperation and participation amongst varying projects. -- jvz. Jason van Zyl [EMAIL PROTECTED] http://tambora.zenplex.org -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
