Re: Splitting Hibernate module from the main release

Eric Pugh wrote:
> One of my challenges with the XDoclet project is the monolithic release
> process.  I was much more active last year, and felt like we made a lot of
> progress on some plugins, including hibernate and the maven plugin.  However,
> because other plugins had less traction, it slowed up the entire release
> process.  I would like to see each plugin released on it's own schedule, and
> the the XDoclet release would consist of the Core plus a selection of plugins
> at various release numbers.   
> 
> This process works very well for the Maven project, indeed the 1.1-beta2
> actually removed a lot of plugins that were not ready.  But, as plugins are
> updated or added, they can be quickly added back to the main build.  
> 
> Anything that reduces coupling between the plugins and Xdoclet itself is a
> good idea.  I'd like to see the split done on a project wide basis. 
> Additionally, this would allow responsibilty for different plugins to devolve
> and spread the load a bit.
> 
> Eric Pugh
> 

Your thoughts echo my own.  There's a lot of ways to package things up, 
maybe the core release shouldn't include any modules, and maybe there 
should be an ejb package that include all ejb modules?  For now, I'm 
just focused on the Hibernate module, that I'd like to see released on 
its own and would package its dependencies: xjavadoc, xdoclet engine, 
and xdoclet module.


-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl