OK, I've implemented the generic module builder. It loops over all modules, checks each module's dependency to other modules, and builds those modules first and then the current module. It's pretty cool! Drop a module under modules folder and just build, no hardcoding in build files. I introduced a module.xml file too. This file is where you specify module dependencies, but can be used for other purposes too. For example instead of coding checkClass() in each SubTask we can define a <class-dependency>javax.servlet.Servlet</class-dependency> there.
Todo: based on this file generate appropriate docs showing the user class dependencies of the module and what other modules this module depends on. I'm not yet up to speed with this anakia/blabla stuff, so someone else (Aslak?) handle it plz. Todo: We've discussed contrib modules. My proposal was to define a contrib.xml file for each contrib. module. Based on it generate appropriate docs that show the user that it's a contrib. module and not directly maintained and supported by xdoclet crew. There we provide mail and site address of the guy who contributed it. Anyone volunteering? Ara. _______________________________________________________________ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas - http://devcon.sprintpcs.com/adp/index.cfm?source=osdntextlink _______________________________________________ Xdoclet-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-devel
