Thanks Mickael for the suggestion... really the UIExtensionTracker was a
very late consequence of the generated p2 installer plan. It was multiple
layers, events and threads away.
We were able to track it down to a custom touchpoint that depends on
some org.eclipse.equinox.p2 bundles.
We were
Hi,
I suggest you enable your application for remote debugging, adding the
`-agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=1044` VM arg
to config.ini; then with your development IDE, connect to this remote Java
application and put breakpoints in UIExtensionTracker.
HTH
I forgot to add the error log with the full stacktraces
On Tue, Nov 23, 2021 at 3:51 PM Martin D'Aloia
wrote:
> Hi all!
>
> We have an Eclipse RCP that we are upgrading to 4.21 (from 4.19) and we
> encountered a problem (that we are not able to find the origin) during the
> Update of our app
Hi all!
We have an Eclipse RCP that we are upgrading to 4.21 (from 4.19) and we
encountered a problem (that we are not able to find the origin) during the
Update of our app via Update Site.
Same code base but upgrading to 4.20 instead of 4.21 works fine.
During the update process, after the
