+1 to all. Judging from all those good reactions about XRAI my highest priority is XRAI atm. I'm trying to finish it in 2-3 days then, some docs updates here and there and then I'm %100 with you. I can't wait for working on xdoclet2! But imho we should be careful about the amount of attention we pay to xdoclet2 discussion before the 1.2 release. Honestly I'm afraid that'll turn us into "xdoclet2 dreamer" or 1.2 will look like "old-fashioned xdoclet 1.2" and so less emphasize on v1.2 quality. *So the highest propriety is still 1.2*.
Ara. > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:xdoclet-devel- > [EMAIL PROTECTED]] On Behalf Of Aslak Hellesøy > Sent: Saturday, October 05, 2002 5:32 PM > To: [EMAIL PROTECTED] > Subject: [Xdoclet-devel] XDoclet 2 structure and process > > Hi folks, > > Over the past six months there has been many discussions on email and > messenger between the developers regarding the new XDoclet Velocity > architecture. Some of us have already started to work on this. > > The build process is currently quite complicated, and we have to improve > that. The way I see it we have two options: > a) Make a new branch in the xdoclet module and start on XDoclet 2 there. > b) Make a new CVS module and code XDoclet 2 from scratch. > > With all the new initiatives (XGG, XRAI, more GUI plugins) + the various > points in Mathias' list > http://users.pandora.be/ees/xdoclet/development/design.html, I think we're > better off going for alternative b). Tag handlers will disappear, we'll > decouple XDoclet from Ant, use Maven for building etc... Trying to tweak > the > current structure would cause too much headache IMO. -And we're talking > about a major version leap, so a complete rewrite is "normal". > > In fact, the XDoclet core will be very thin, since plugins and xjavadoc > contain most of the logic. XDoclet will only be glue. > > So my proposal is to create a new module called xdoclet2 where we can > start > from scratch and do things "right". Ara and I have already discussed this, > and we have come up with a structure proposal: > > xdoclet2 > core (now) > plugins (now) > ejb (now) > jboss-ejb (later) > jboss-web (later) > jakarta-struts (later) > bea-wls-web (later) > bea-wls-ejb (later) > bea-wls-cmprdbms (later) > samples (soon) > xgg (now) > xdocletgui (later) > xjavadoc (later) > xrai (now) > > Some explanations: > -Let's use the term "plugin" in stead of "module". That's what they are, > isn't it? > -Each component should provide their own documentation (xdoc). > -There will be one plugin for each DTD/XML > -Everything will be built by Maven (compilation, jarring...) > -There will be JUnit tests everywhere > > So this is a proposal about a return to "one-module" CVS structure. What > do > you think about this? > > I am working on a new ejb module using a structure similar to this, based > on > Velocity/XGG. The intention is that it will serve as a proof-of-concept > and > a template "best practice" structure for all the other plugins. > > Aslak > > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _______________________________________________ > Xdoclet-devel mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/xdoclet-devel ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Xdoclet-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-devel
