> -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] > Sent: 4. januar 2003 17:01 > To: Turbine Maven Users List > Subject: RE: 2 qs about Xdoclet plugin > > > Aslak Hellesoy <[EMAIL PROTECTED]> wrote on 05/01/2003 01:16:27 AM: > > > > > Please send patches to the XDoclet plugin to XDoclet > > http://opensource.atlassian.com/projects/xdoclet and _not_ to the Maven > > team. The reason being that the jelly script is in fact generated by > XDoclet > > itself. IIRC, we agreed before xmas that it should be the XDoclet team's > > responsibility to maintain the plugin. > > That's not what Ara wanted: > > http://www.mail-archive.com/[email protected]/ > msg02312.html >
With "Ouch don't do that!" I believe Ara was referring to the sentence "-So you can remove the XDoclet plugin from Maven's CVS", but not to the previous sentences in the same paragraph. Please read it again. (And Ara, correct me if I'm wrong). The people who maintain the XDoclet Maven plugin (currently Ara and I) have to be XDoclet committers, because the jelly script is generated by XDoclet itself (by looking at the XDoclet sources and using a special XDoclet template), so it just can't be moved to Maven's CVS. Well, it can, but it would require anybody bulding the plugin to have XDoclet's sources handy. -Which makes things very complicated, and I doubt anybody would want it that way. So the XDoclet team maintains the XDoclet template that generates the jelly script. -And wraps up the maven plugin as a jar file. When people find errors, they tell us, we modify the template and generate a new plugin. Ara suggests we provide the Maven team with updated plugins every time XDoclet is released. I think this would make life more complicated for both the XDoclet team and the Maven team, and I disapprove with Ara's suggestion. The only drawback I can see with keeping everything in XDoclet's CVS and distro (and nothing in Maven) is that the plugin will have to be installed manually. -But AFAIK, automatic downloading and installation of plugins is a planned feature in Maven. When/if this is implemented, this drawback will vanish. And in the meanwhile I think people can live with a manual installation of the plugin. After all it's just a matter of copying the plugin jar file from the XDoclet distro to Maven's plugin directory. What do you think? Aslak > > > -- > dIon Gillard, Multitask Consulting > Blog: http://www.freeroller.net/page/dion/Weblog > Work: http://www.multitask.com.au > > > > -- > To unsubscribe, e-mail: > <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: > <mailto:[EMAIL PROTECTED]> > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
