[mojo-dev] [jira] (MJAXB-103) Add structured post-processing pipeline to handle Javadoc-to-XML Documentation

[JIRA]

Title: Message Title

Lennart Jörelid commented on an issue   Re: Add structured post-processing pipeline to handle Javadoc-to-XML Documentation While we could certainly make this move in the 2.0 release, the consequences are somewhat problematic. Plexus DI mechanics (as is used by Maven plugins) require that each implementation class in a chain-of-command configuration parameter (i.e. Array or List) be named explicitly. This makes the configuration verbose, although arguably clear. If the current three optional post-processing steps could be said to cover the absolute majority of prost-processing steps, we would not need to increase the configuration burden on users by requiring them to supply the FQCN for each implementation class. I will therefore refrain from making the post-processing steps be implemented as a chain of command for the 2.0 release. Add Comment   Mojo's JAXB-2 Maven Plugin / MJAXB-103 Add structured post-processing pipeline to handle Javadoc-to-XML Documentation The Schemagen tool used by JAXB lacks several important features # XSD has a standard documentation structure for ComplexTypes and Elements. JavaDoc has a standard documentation structure for Classes and Methods. But the SchemaGen tool can not copy JavaDoc documentation to generated XSD structures, as it processes compiled bytecode where the JavaDoc i... This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c) --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email