lipse (e.g. specify config.ini option osgi.debug= or use -debug launch option).>> Tom> > > - Original message -> From: Martin Lippert > Sent by: equinox-dev-boun...@eclipse.org> To: Equinox Dev > Cc:> Subject: [EXTERNAL] Re: [equinox-dev] understanding resolving re
er=true
>
> At this point I assume you know how to enable trace for Eclipse (e.g. specify
> config.ini option osgi.debug= or use -debug launch option).
>
> Tom
>
>
> - Original message -
> From: Martin Lippert
> Sent by: equinox-dev-boun...@eclipse.org
>
Hey Mickael,
> So I am looking for strategies to debug and understand this.
>
> Have you tried starting with the `-console` flag to use the OSGi console and
> compare the effect of the "start" action on both packages?
Thanks for the suggestion, not sure I understand this.
Doing a “start” on a
On Wed, Jun 12, 2019 at 12:05 PM Martin Lippert wrote:
> So I am looking for strategies to debug and understand this.
Have you tried starting with the `-console` flag to use the OSGi console
and compare the effect of the "start" action on both packages?
Hey!
I am trying to understand a somewhat strange setting. I have two Eclipse
installs with an identical set of bundles. Nevertheless, the dependency
resolution is different (just fine for one case,
package-use-constraint-violation in the other case). Therefore I am trying to
understand why
