> I think it would be possible to include the examples in the Ant source > too - this would make it even more clear what the code is trying to > accomplish and would hep to prevent refactorings etc that go against the > intended use of the code. > > My thought would be to include at the top of the class, an @ant.category > to get us started, then for example something like > > @ant.usage.begin > lots of correctly formatted xhtml..... > @ant.usage.end > > @ant.build.begin > lots of correctly formatted ant xml > @ant.build.end > > Thoughts?
-1. I hate all the < > entities used in example. I think I've already demonstrated in Ant's SVN repo that examples can be written as XML in the 'future' XML doco, where it's a natural fit, as opposed to being shoe-horned into the .java files. There's lots of value to describe individual attributes or elements directly from the corresponding method Javadocs, but this should later be merged with the manually maintained XML doco file for the task/type, containing the examples. --DD --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
