RE: [mylyn-integrators] Problem with connector plug-in dependency onorg.

["Tom Bryan (tombry)" <tombry@xxxxxxxxx>]

Steffen Pingel wrote on Wednesday, September 10, 2008 1:44 AM:

> You are most likely running into this bug:
> 
> 157375: PDE should support building against nested JARs
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=157375

Bingo!  That's exactly the problem I was hitting.

By the time I got your message, I had figured out that the problem
involved unpacked plug-ins that contain nested JARs (by comparing it
with the org.junit plug-ins), but I hadn't tested the theory, yet.  I
*completely* agree with Mik's comments in that bug:  "[PDE Build]
currently [does] this so amazingly well that users end up getting quite
confused by this one case where they don't."  

> A possible workaround that I have seen is to add the httpclient jar
> to your plug-in and specify it as an extra class path entry in the
> build.properties. The jar is only used for compiling and not needed
> during runtime if a dependency on org.eclipse.mylyn.web.core is
> specified in your plug-in. 

Got it.

> It might also work to extract the org.eclipse.mylyn.web.core plug-in
> to avoid nested jars.

Interesting idea, but that creates a long term "tweak" in our build
environment that I'd like to avoid.  

> If you don't need the utility classes for httpclient that are
> provided by org.eclipse.mylyn.web.core you can also consider
> consuming httpclient from the org.apache.commons.httpclient Orbit
> bundle. For Mylyn 3.0 all 3rd party library dependencies are consumed
> from Orbit bundles which do not nest jars but contain class files or
> are unpacked (e.g. org.apache.axis) when installed.

Thanks, I didn't know about Orbit.  Since we'll be moving our connector
to Mylyn 3.0 later this month, that's probably the best approach.

-- 
Tom Bryan <tombry@xxxxxxxxx>
Cisco Systems