> > I remember that you (Gavin) mentioned that the Xdoclet team would take > > over the Hibernate task. Is that going to happen? I see some project > > branching going on there towards some Jakarta templates too. > > Ara will accept the Hibernate module into their codebase but we would need > to maintain it ourselves with *no* CVS access (at least initially). I > would > much prefer it to live in their CVS repository but I am unwilling to > maintain the code myself using patches. I am very keen for this code to > find > itself an "owner" since I have enough on my plate with the persistence > engine. The rest of our toolset was created and is being mainly maintained > by other people and I would like to see the same happen here.
Ara is himself here to help :-) I'm involved in a project that probably (90%) will use Hibernate. So I'll have to use it myself and be sure I can't resist contributing to open source projects :-) So wherever the module ends up in I'll contribute. I think it's better for it to live in hibernate's cvs. Btw, as described previously in xdoclet-devel we'll probably set up a smart distributed module build system using Maven in xdoclet2. So you'll host the module in hibernate's cvs, but we'll checkout it, build it and bundle it and even test it. This way we'll be able to keep an eye on what's going on in remotely hosted modules and still keep it separated. Ara. ------------------------------------------------------- This sf.net email is sponsored by: See the NEW Palm Tungsten T handheld. Power & Color in a compact size! http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en _______________________________________________ hibernate-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/hibernate-devel
