Hi. I am ready to commit sources for an xdoclet gui I've been working with. (It's not Middlegen, it's the one you can see a picture of in the new tools.html I committed a few days ago). -But where to?
The way I see it, there are at least 4 options for new sub projects: a) Put it in xdoclet CVS module under xdoclet/core/src, but in a separate package, for example xdoclet.subproject.* b) Put it in xdoclet CVS module under xdoclet/subproject/src (still using xdoclet.subproject.*) c) Make a separate CVS module, as with xjavadoc d) Make a completely different project (as with middlegen) Here are my considerations about xdoclet gui: a pro) very easy to start working without having to rework ant scripts. makes it easy to bundle gui with core in the same jar. a con) perhaps we don't want gui/core so close to each other? b pro) dependent jars can be shared between xdoclet core and xdoclet gui b con) distro is coupled with xdoclet, although code might not be. c pro) it can easier live a life of its own. c con) it can easier live a life of its own. c con) no reuse of jars/ant scripts d pro) i can put my own licence on it and sell it for big bucks d con) it will confuse people -For xdoclet gui, I'm in favor of b) That's how ant did with antidote (ant gui). When it got too big, they moved it to a separate module. We can do that too if it ever happens. -For reverse xdoclet, I'm in favor of a) since it is very natural to bundle this with the core. -For xtags I don't know. What do you think? Konstantin's xtags seems pretty similar to a subpackage of my xdoclet gui, although I must admit I haven't really understood what xtags does. (The similarity lies in describing tags in a meta xml file, not the implementation). Let's get this stuff into CVS *NOW* before we all paint ourselves into our own little corners ;-) Aslak _______________________________________________ Xdoclet-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-devel
