I also think it's a good idea to keep a copy in Maven, but let the XDoclet team be responcible for improvements and patches. Has anybody else tried the current XDoclet plugin (which is now in XDoclet's CVS)? Is it good enough now?
Aslak > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] > Sent: 12. desember 2002 23:55 > To: Turbine Maven Users List > Cc: [EMAIL PROTECTED] > Subject: RE: XDoclet + Maven. What's where? > > > So are you sure now? > > -- > dIon Gillard, Multitask Consulting > Blog: http://www.freeroller.net/page/dion/Weblog > Work: http://www.multitask.com.au > > > Ara Abrahamian <[EMAIL PROTECTED]> wrote on 10/12/2002 10:00:44 PM: > > > > I have also moved the Maven XDoclet plugin documentation and the > > > build of > > > the plugin itself into XDoclet's CVS. XDoclet's build system now > > > produces a > > > maven-xdoclet-plugin-1.2b2.jar. -So you can remove the XDoclet plugin > > > from > > > Maven's CVS. > > > > Ouch! No, don't do that! We'll keep the master copy in xdoclet's cvs > > and just submit patches to maven in every release. So Maven will have > > an xdoclet maven plugin built-in but the master sources where we change > > and play with are in xdoclet's cvs. > > > > Ara. > ------------------------------------------------------- This sf.net email is sponsored by: With Great Power, Comes Great Responsibility Learn to use your power at OSDN's High Performance Computing Channel http://hpc.devchannel.org/ _______________________________________________ Xdoclet-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-devel
