PDE can have compile time dependencies in its build.properties but naturally
build.properties is not part of the final jar
Tom
Von meinem iPhone gesendet
> Am 09.05.2015 um 00:52 schrieb Stephan Herrmann :
>
> I'm not responding to any of that religious anti-PDE flame war
> which is totally i
I'm not responding to any of that religious anti-PDE flame war
which is totally inappropriate in this discussion.
On 05/08/2015 10:21 AM, BJ Hargrave wrote:
Well I suggest that (1) JDT not have a fatal error here since the goal is not
to generate a class file
Sounds like the obvious way to g
Alex is correct. Things in the STARTING state are waiting to be lazily activated on first class define.Tom-equinox-dev-boun...@eclipse.org wrote: -To: Equinox development mailing list From: Alex Blewitt Sent by: equinox-dev-boun...@eclipse.orgDate: 05/07/2015 04:40PMSubject: Re: [equinox-d
There are Eclipse-specific classes in o.e.osgi such as NLS and Debug which
makes it hard to do what you suggest, especially since these are provided in a
supplements bundle which cannot co exist in an eclipse runtime.
Alex
Sent from my iPhat 6
> On 8 May 2015, at 09:21, BJ Hargrave wrote:
>
> From: Stephan Herrmann
> On 05/07/2015 05:21 PM, BJ Hargrave wrote:
> > > User has an arbitrary plugin project which obviously depends
ono.e.osgi.
> >
> > Well I would say that no one should depend upon org.eclipse.osgi.
> It is an implementation of the OSGi core spec. If you are writing
> >
> From: Markus Keller
> I think we had the same discussion about a year ago:
>
> Bug 436469: Declare compile-time (build-time) dependencies in manifest
> Bug 434243: Import org.eclipse.osgi[.services] as source => compile
> errors for missing @ConsumerType
>
> The problem is still the same:
