Skip to main content

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

Thanks Igor!

With <debug>true</debug> in the JavaDoc plug-in I found the cause. It's the stupid doclet that is broken on Windows. Tycho is passing the right classpath to the Maven JavaDoc plug-in. The Maven JavaDoc plug-in converts that into an argument for the JavaDoc tool. Of course, the argument uses ';' as path separator on Windows. The stupid doclet has ':' hard coded. :(


Am 06.06.2013 13:38, schrieb Igor Fedorenko:
Generally, Tycho is expected to inject bundle dependencies back into
maven model as <dependency> elements. This does not happen for
dependencies with nested jars, but otherwise this should just work. If
you can provide a small standalone example that shows the problem, I can
have a quick look to see what's going on exactly.


On 2013-06-06 7:27 AM, Gunnar Wagenknecht wrote:

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
[WARNING] ...ResourceDoclet getSerializedLinkFromTag
[WARNING] INFO: Have system classloader class
[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(

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

Is that possible?


Gunnar Wagenknecht

Back to the top