This is another example: http://htmlunit.sourceforge.net/dependencies.html
the htmlunit dependency report is generated applying an xsl stylesheet directly to the pom. Dependencies group are generated using a property tag in each dependency listed in the POM. Whatever solution will be chosen it should be enough flexible to solve different problems: - specify the scope for the dependency (compile/run/test/report) - specify if it's required or optional (and "required if") - group together dependencies with the same scope in the dependency report - allow an addictional comment where you can specify why a dependency is needed probably the 1� goal can be achieved by a specific tag in the dependency element, others can be solved playing with already existing properties. Allowing users to easily select a different velocity/xslt template (which should have access to all the properties in the dependencies listed in the pom) is the best way to provide some addictional flexibility. This could be a fast/easy solution while waiting to address some of the requirements in a more structured way in future. fabrizio On Fri, 26 Nov 2004 07:34:58 -0200, Felipe Leme <[EMAIL PROTECTED]> wrote: > On Fri, 2004-11-26 at 03:22, Michal Maczka wrote: > > I don't think that XML comments are sufficient here. > > I agree. > > > First of all I'd like to see those comments propagated to documenatation > > (website, pdf etc) sometimes they are quite important... > > That's right. Take a look in the Display Taglib as an example: > > http://displaytag.sourceforge.net/dependencies.html > > -- Felipe > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
