On 30 Apr 2002, Stefan Bodewig <[EMAIL PROTECTED]> wrote: >> did you try doing a test run of our own xdoc proposal? > > Honestly, no. I'll try it.
OK, I see where the problem is from javadoc's point of view - all files are specified as source files and all packages are specified as well, making javadoc barf because it parses the same sources twice. But now that I have tried to follow the full inheritance chain, I'm completely puzzled. <xdocs> inherits from a class in xdoclet which (indircetly) inherits from a class in xjavadoc which in turn inherits from <java> - our <javadoc> task is not involved at all as far as I can tell, so I don't see how any changes in it can break <xdoc>. My observations are based on the xdoclet and xjavadoc sources residing on the box that runs Gump builds for me, i.e. the latest CVS versions. I don't know how/if these are different from the jars checked into the proposal tree. Right now, I don't think that the changes to javadoc are related to the xdocs proposal at all. Stefan -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
