Hi,
It's probably easier to parse those sources with QDox[1], like we do with
maven-plugin-tools.
I've become the project lead of this project, so if you need help just let
me know.
Robert
[1] http://qdox.codehaus.org
Op Mon, 29 Dec 2014 16:36:21 +0100 schreef Lennart Jörelid
<[email protected]>:
Hello all,
I need to enhance the Jaxb2 Maven Plugin to optionally merge JavaDoc
comments into XSDs generated from JAXB-annotated classes. In order to do
this, I need to develop a custom Doclet - and unit test it, just like I
do
all other code I develop.
*Alas:* What's the best practise for setting up Doclet tests in a Maven
project?
*Condition:* I don't want to resort to AbstractMojoTestCases, as I am not
attempting to create reports. I would simply like a plain jUnit testcase
for a Doclet.
*Background*
This custom Doclet is not intended to generate Maven documentation, but
instead to perform postprocessing of java sources to inject javadoc
comments into generated XSDs on the form shown below:
/**
* Some information here...
*/
@XmlType(namespace =
"http://www.jguru.se/foobar";)@XmlAccessorType(XmlAccessType.FIELD)public
class SomeType { ... }
... should yield ...
<xs:complexType name="someType">
<xs:annotation>
<xs:documentation>
Some information here...
</xs:documentation>
</xs:annotation>
<xs:complexContent>
....
The issue opened is http://jira.codehaus.org/browse/MJAXB-103.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
