---------- Forwarded message ----------
From:
Eclipse Webmaster (Denis Roy) <webmaster@xxxxxxxxxxx>Date: Thu, Mar 31, 2016 at 6:50 PM
Subject: Re: Eclipse CHE signing issue
To: Roman Iuvshin <
riuvshin@xxxxxxxxxxx>, Wayne Beaton <
wayne@xxxxxxxxxxx>, Mikaël Barbero <
mikael@xxxxxxxxxxx>, Tyler Jewell <
tjewell@xxxxxxxxxxx>, Stevan Le Meur <
slemeur@xxxxxxxxxxx>, Sergii Kabashniuk <
skabashnyuk@xxxxxxxxxxx>, Gennady Azarenkov <
gazarenkov@xxxxxxxxxxx>
Hi Roman,
Your best bet is to ask on the cbi-dev mailing list. Perhaps someone
else has run into that issue (either at Eclipse or within their
corporation) and can offer some guidance.
https://dev.eclipse.org/mailman/listinfo/cbi-dev
Denis
On 03/31/2016 11:43 AM, Roman Iuvshin wrote:
> Hi guys,
> We faced with issue that CHE does not work after jar signing procedure.
> The problem is that we are heavily using google guice framework which
> doing some class modification in runtime and it fails:
>
> Caused by: java.lang.SecurityException: class
> "org.eclipse.che.plugin.docker.machine.DockerInstanceProvider$$EnhancerByGuice$$9762f377"'s
> signer information does not match signer information of other
> classes in the same package\
>
>
> FYI I've redeployed CHE bundles with not signed ones on eclipse download
> server until we will find any solution.
>
>
