I have made a tag BEFORE_MODULE_RAFACTORING_TAG and a branch MODULE_REFACTORING_BRANCH and I'm currently working on it. I'll commit some stuff tomorrow. Then it's easier for all of us to have something concrete to discuss. I'm game for a Yahoo Messenger session somewhere between 1800 GMT and 2000 GMT. Those of you who want to attend should distribute your Yahoo Messenger ids and make sure you have a client that supports conferences. Hope to hear from you all tomorrow!
Bye, Aslak > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of Ara > Abrahamian > Sent: 24. april 2002 21:26 > To: [EMAIL PROTECTED] > Subject: [Xdoclet-devel] modules > > > Well, imho it's absolutely ok to group some modules (group > jboss-ejb/jbossweb/etc under module jboss). But I insist that we should > remove the word "core" and "optional" from the directory structure. > *Don't forget the intent is to make adding new modules plug-and-play*. > So here is the detailed proposal: > > Xdoclet > Core (all core stuff, no modules AT ALL, nothing even xdoclet.ejb.*) > Src > xdoclet > xdoclet.template > xdoclet.util > xdoclet.loader > Tests > Script > Samples > .... > modules > jboss > web > src > tests > docs > script > samples > src > script > blabla > ejb > src > tests > docs > script > samples > src > script > blabla > ejb > (entitypk,entitycmp/bmp,deploymentdescriptor,dataobject...) > core > src > tests > script > samples > src > script > blabla > xml-rpc > same as above > > So I'll be able to drop in my xml-rpc stuff as a whole under modules. > The xdoclet/script/build.xml decides which modules are core which are > optional. And if I write JDO templates then again a new group and > module. And if I want to add templates for OpenFusionJDO then I can: > either put it under a top level module (modules/OFJDO) or put it under > JDO module (modules/JDO/OFJDO, while core JDO stuff in > modules/JDO/core). > > So the script/build.xml of a module will have a classpath like this: > > <!-- Set up project.class.path --> > <path id="project.class.path"> > > <fileset dir="lib"> > <include name="**/*.jar" /> > </fileset> > > <!-- root --> > <fileset dir="../../lib"> > <include name="**/*.jar" /> > </fileset> > > <!-- xdoclet.jar --> > <fileset dir="../../core/dist/lib"> > <include name="xdoclet.jar" /> > </fileset> > > <!-- append the external classpath lastly --> > <pathelement path="${java.class.path}" /> > > </path> > > And we can use the trick from Erik's forthcoming book to define these > repeating stuff in a separate xml file and include that xml file in > each module's build file. > > PS: Let's decide soon! It doesn't happen much these days for me to find > some time to write some xdoclet code! I want to finish the xml-rpc/jdo > stuff and commit them before getting ultra-busy again :-) > > Ara. > > > __________________________________________________ > Do You Yahoo!? > Yahoo! Games - play chess, backgammon, pool and more > http://games.yahoo.com/ > > _______________________________________________ > Xdoclet-devel mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/xdoclet-devel _______________________________________________ Xdoclet-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-devel
