Hi, Am Sonntag, den 13.01.2008, 15:02 +0100 schrieb Roland Weber: > However, I strongly suggest that you don't put 22 artifacts on > separate release cycles.
Definitely agree here :-) > Every release comes with some overhead > in preparing release notes, reviewing the artifacts, voting on > the release, performing the release, sending the release mail, > and updating the web page. That may not seem much while you're > dealing with one release for all artifacts, but if you multiply > that overhead twentyfold, you'll feel the pain. It will also > get you and your users into dependency hell. Felix should be > able to tell you a story or two about that from Apache Felix. > IIRC, the next release of the maven-bundle-plugin depends on > several other releases that have to be done first. Well, I agree that the maven-bundle-plugin is a dependency hell. But this is just one project and probably the one with the most dependencies. In addition, it is only the first time that we have much overhead. Later on there will be less. Of course, we are in a better position in Felix as we have the OSGi API which is pretty stable and have projects which are more or less independent on each other. > I recommend > to shoot for a manageable 5 or 6 independent release cycles. +1 Regards Felix > Without knowing the internals of Jackrabbit, for example: > - base/common/util classes used almost everywhere > - repository API and SPI > - repository implementation(s) > - remoting > - WebDAV > - ? > I hope you get the idea. I know that the WebDAV component > itself has a base, client and server section. Likewise, the > remoting stuff surely has a client and a server section. > But releasing one without the other is not likely, right? > Splitting the code into components and packaging it into > separate JARs is still possible if they are on the same > release cycle. That's what JIRA components are good for. > > cheers, > Roland > > [1] http://www.apache.org/dev/project-creation-tasks.html >
