Re: [tycho-dev] Make Jersey's custom JavaDoc doclet ResourceDoclet Tycho

["Sievers, Jan" <jan.sievers@xxxxxxx>]

you could try the maven-dependency-plugin:build-classpath goal with outputProperty and use that property [1].

Or ${maven.compile.classpath} with maven-antrun-plugin [2].

Regards,
Jan

[1] http://maven.apache.org/plugins/maven-dependency-plugin/build-classpath-mojo.html#outputProperty 
[2] http://maven.apache.org/plugins/maven-antrun-plugin/examples/classpaths.html 

-----Original Message-----
From: tycho-dev-bounces@xxxxxxxxxxx [mailto:tycho-dev-bounces@xxxxxxxxxxx] On Behalf Of Gunnar Wagenknecht
Sent: Donnerstag, 6. Juni 2013 13:41
To: tycho-dev@xxxxxxxxxxx
Subject: Re: [tycho-dev] Make Jersey's custom JavaDoc doclet ResourceDoclet Tycho-aware

Am 06.06.2013 13:27, schrieb Gunnar Wagenknecht:
> 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.

FWIW, it seems that ${project.compileClasspathElements} contains what I 
need. However, I can't use this one out of the box. It's added as 
"[...jar, .....jar, ...]" whereas the doclet expects "...jar:...jar" syntax.

Additionally, the -classpath element seems to be added to the 
commandline already by the Maven JavaDoc plug-in. I wonder if that is 
the wrong (non-OSGi aware) classpath already.

-Gunnar

-- 
Gunnar Wagenknecht
gunnar@xxxxxxxxxxxxxxx
http://wagenknecht.org/

_______________________________________________
tycho-dev mailing list
tycho-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/tycho-dev