Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[tycho-dev] Make Jersey's custom JavaDoc doclet ResourceDoclet Tycho-aware


I'm looking for some guidelines/best practices in order to make a custom doclet aware of a Tycho computed dependency tree for a project.

My use-case is to integrate the Jersey ResourceDoclet into a Tycho build. That works mostly. However, some of the classes processed by ResourceDoclet references classes from other bundles. It seems that the Jersey ResourceDoclet isn't capable of loading them.

[WARNING] ...ResourceDoclet getSerializedLinkFromTag
[WARNING] INFO: Have classloader: class
[WARNING] ...ResourceDoclet getSerializedLinkFromTag
[WARNING] INFO: Have thread classloader class com.sun.jersey.wadl.resourcedoc.ResourceDoclet$Loader
[WARNING] ...ResourceDoclet getSerializedLinkFromTag
[WARNING] INFO: Have system classloader class sun.misc.Launcher$AppClassLoader
[WARNING] ...ResourceDoclet getSerializedLinkFromTag
[WARNING] SEVERE: Could not get field ...Examples.SAMPLE_ERROR
[WARNING] java.lang.ClassNotFoundException: ....RestExamples
[WARNING] at Method)
[WARNING] at java.lang.ClassLoader.loadClass(
[WARNING] at java.lang.ClassLoader.loadClass(
[WARNING] at java.lang.Class.forName0(Native Method)
[WARNING] at java.lang.Class.forName(
[WARNING] at com.sun.jersey.wadl.resourcedoc.ResourceDoclet.getSerializedLinkFromTag(

I have two options now. Either I patch ResourceDoclet to make it aware of a Tycho-Maven computed classpath of the project it runs in or I somehow confince Tycho to dump the computed project classpath as a string variable which I could pass via -classpath option to the ResourceDoclet.

Is that possible?


Gunnar Wagenknecht

Back to the top