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

Reply via email to