Hello all,
The solution proposed by Tom works for me.
It leverages on the OSGi services to contribute the classpath entries – so each classpath entry provider must register as a service.
So far so good.
The question is : as the contribution part usually is done via extension points (at least this is the case with org.eclipse.pde.internal.core.RequiredPluginsClasspathContainer),
what are the chances for the Tom’s proposed solution to get into next Eclipse release?
Can I stick to it, or I just need to wait or contribute a new extension point?
Best regards,
Vladislav
From: pde-dev-bounces@xxxxxxxxxxx [mailto:pde-dev-bounces@xxxxxxxxxxx] On Behalf Of Curtis Windatt
Sent: Thursday, November 17, 2011 7:08 PM
To: Eclipse PDE general developers list.
Subject: Re: [pde-dev] [Question] : How to extend PDE classpath provider
Hi Vladislav,
Can you please look at Tom's enhancement and let us know whether it solves your issue?
Curtis
From: | Tom Schindl <tom.schindl@xxxxxxxxxxxxxxx> |
To: | "Eclipse PDE general developers list." <pde-dev@xxxxxxxxxxx>, |
Date: | 2011/11/17 10:37 AM |
Subject: | Re: [pde-dev] [Question] : How to extend PDE classpath provider |
Sent by: | pde-dev-bounces@xxxxxxxxxxx |
Hi,
I've had the same problem and filed:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=363733 though my usecase
is bit different in the end it does exactly what you want.
For 3.7.1 I implemented a feature patch [1,2,3] but I hope I can work
with the PDE people on getting this in for 3.8.
Tom
[1]https://github.com/tomsontom/e-fx-clipse/tree/master/at.bestsolution.efxclipse.tooling.pde.fragment
[2]https://github.com/tomsontom/e-fx-clipse/tree/master/at.bestsolution.efxclipse.runtime.osgi
[3]https://github.com/tomsontom/e-fx-clipse/tree/master/at.bestsolution.efxclipse.tooling.pde.ui
Am 17.11.11 17:24, schrieb Iliev, Vladislav:
> Hello all,
>
>
>
> This is my first e-mail in this mailing list, so I’m kind of a newbie J
>
>
>
> I went through a debugging of some PDE classes especially classpath
> initializers and classpath entry providers.
>
> I wanted to contribute to 2 given classpath container providers, so I
> can attach additional information (like java doc) to the classpath
> entries in method getClasspathEntries.
>
>
>
> First I had to do this for a pure web projects and I did it by
> contributing to the extension point
>
> org.eclipse.jst.server.core.runtimeClasspathProviders and by extending
> org.eclipse.jst.server.core.RuntimeClasspathProviderDelegate and
> attaching the corresponding javadoc_location classpath entry attribute.
>
>
>
> Now I would like to do the same for PDE based projects. I started to
> look around for the same extension point, but with no luck.
>
> As far as I researched the classpath initializer
> (org.eclipse.pde.internal.core.RequiredPluginsClasspathContainer) for
> the PDE projects in its initialize method is not meant to
>
> consider any custom classpath providers as the classpath for the pure
> web projects
> (org.eclipse.jst.server.core.internal.RuntimeClasspathContainerInitializer)
> does.
>
> The PDE classpah initializer assumes that the java doc for a given
> plugin is located inside the plugin under /doc/ folder.
>
>
>
> Any hints on how I can extend the classpath provider for PDE projects
> will be much appreciated.
>
>
>
> Cheers,
>
> Vladislav Iliev
>
> tel.: +359 8056 753
>
> e: vladislav.iliev@xxxxxxx <mailto:vladislav.iliev@xxxxxxx>
>
>
>
>
>
> _______________________________________________
> pde-dev mailing list
> pde-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/pde-dev
--
B e s t S o l u t i o n . a t EDV Systemhaus GmbH
------------------------------------------------------------------------
tom schindl geschäftsführer/CEO
------------------------------------------------------------------------
eduard-bodem-gasse 5-7/1 A-6020 innsbruck fax ++43 512 935833
http://www.BestSolution.at phone ++43 512 935834
_______________________________________________
pde-dev mailing list
pde-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/pde-dev
