Peter, Love it. If it can, I think it should go into general use and build into build/classes/
I have a concern. For a few blocks of mine where I have two impls of the same thing, I often use an abstract parent class to do the common stuff. For those cases, the @phoenix:dependency comments should be complete in the subclasses as XDoclet cannot look into the parent class, yes? Regards, - Paul H >I just went and put together an example of using xdoclet to generate the >blockinfo files for a block rather than having them be hand-maintained. To >look at the results gointo the cornerstone project and type > >ant xdoclet > > >It will generate a descriptor in gen/ hierarchy. It is not yet integrated >fully into the build and I am not yet 100% sure on how we should go about >doing that but have a look at it and see what you think. > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
