> > Hi, > > +1 for Docbook > > +1 for the minimum hand coding as well. > > I will have a look how a Subtask could be docletted (in the docu > > sense) but
Look at Erik's @ant:task/... code first :-) Use it, and if something is missing add to it, and make it generic. I don't find anything xdoclet-specific here, only that xdoclet has lots of subtasks. > Ara, IIRC you had some plans about "merging" DocletTask and SubTask. > Will this have an impact on the job of docletting SubTask? I don't know exactly. What I can say right now (no code on hand, just some thoughts) is that tasks and subtask instead of being derived from ant's Task or whatever will be derived from a common interface. So in your task you should make this "interface name" configurable. So we'll have just one XDocletAntTask class, it'll rely on dynamicconfigurer solely, looking up attributes/elements in the contained task class (which as I've said before is not an Ant Task, but derives from an XDocletTask class, subtasks also derive from it, it's a composite). You get the idea: loop over XDocletTask-derived class. Parent parameter of @xdoclet:subtask will be just a suggestion or better to say just for documentation and logical grouping, all subtasks can right now be embedded in other doclets too. There are some limitations in this regard (dependencies to other related subtasks or presence of some doclet level parameters), but the moral of the story is: you can do that in code level, though consider the dependencies of each subtask. We can do the transition from @xdoclet:subtask to @xdoclet:task too, or maybe just call XDocletTask, well, XDocletSubTask :-) For now write a task which accepts a set of class names. Loop over them and introspect them, generate xmls for each one. Now the tricky part is: assuming you use Erik's code, there's some hard dependencies there to Ant and the way Ant works (in Ant you can define a Task by just putting an execute() method there, no need for deriving from Task). So extract this Ant-specific code to an strategy class, you activate it with an <ant-strategy/> nested element of <documentor/>/whatever-you-name-it. Note that I haven't looked at Erik's code yet, but it should be a high quality one I assume :-) > Aslak 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 _______________________________________________ Xdoclet-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-devel
