Leo Simons wrote: > > +1 with some comments..... > > > 'printerdocs' > > This generates a printer friendly version of the documentation. > > Most projects dynamically build their documentation from XML > > anyway. They should provide a nice and simple stylesheet that > > avoids all the HTML tables embedded in tables approach most > > site docs use. > > While I agree, I am not sure whether this should be a required part > for all projects (ie a very small project that generates a single > jar and some javadoc shouldn't have to bother) so this should be an > optional part.
Point taken. In that case, it would mirror what docs does. But as soon as a project starts producing output, the printable docs are invaluable. > On javadocs....it would be useful to have a mechanism where you can > specify other locations for javadocs to link to using .ant.properties. > Would it be smart to standardise this too? You have a suggestion? > > 'check' > > This target is used to compile and execute any unit tests that > > are built into the project. > > would remove "unit" there. Not everyone has come around to the concept > yet ;-) Gotcha! --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
