[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cbi-dev] Eclipse CHE signing issue

Hi Roman,
it doesnât seem to be a guice related issue.
You need to make sure that all the classes with package: âorg.eclipse.che.plugin.docker.machine"
loaded by the classloader are signed. 
You can use jarsigner -verify for all your org.eclipse.che.* jars to make sure they are properly signed

Best regards,
Am 31.03.2016 um 17:57 schrieb Roman Iuvshin <riuvshin@xxxxxxxxxxx>:

---------- 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.



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.

cbi-dev mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit

Viele GrÃÃe,
Dennis HÃbner

Attachment: signature.asc
Description: Message signed with OpenPGP using GPGMail