[jbosstools-issues] [JBoss JIRA] (JBIDE-22992) OpenShift tools use wrong rest client bits

Nick Boldt (JIRA) issues at jboss.org
Wed Aug 10 15:02:00 EDT 2016


    [ https://issues.jboss.org/browse/JBIDE-22992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13277517#comment-13277517 ] 

Nick Boldt commented on JBIDE-22992:
------------------------------------

{quote}Could we customize the way the hash is computed to include also the content of the lib folder?{quote}

We don't publish the lib folder to /snapshots/ -- we only publish the generated update site -- so there's no way to diff that remote lib folder against the latest workspace folder. We could, I suppose, but we don't do that today.

What if the build hardcoded a specific version of the snapshot jar, eg., 5.0.0-20160809.161416-8? 

That way, a maven enforcer rule could fail the build if a newer version was found in Nexus. Then you'd guarantee that for every snapshot change, you'd have to actually absorb the new version and verify it works... rather than just pulling in the latest and assuming it's fine.


> OpenShift tools use wrong rest client bits
> ------------------------------------------
>
>                 Key: JBIDE-22992
>                 URL: https://issues.jboss.org/browse/JBIDE-22992
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: build, openshift
>    Affects Versions: 4.4.1.AM3
>         Environment: eclipse.buildId=10.1.0.AM3-v20160810-0441-B5735
> java.version=1.8.0_101
> java.vendor=Oracle Corporation
> BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_US
> Framework arguments:  -product com.jboss.devstudio.core.product
> Command-line arguments:  -os win32 -ws win32 -arch x86_64 -product com.jboss.devstudio.core.product
>            Reporter: Denis Golovin
>            Assignee: Jeff MAURY
>            Priority: Critical
>             Fix For: 4.4.1.Final
>
>
> An internal error occurred during: "Loading service-manager to configure additional frameworks that CDK depends on.".{code}java.lang.NoSuchMethodError: com.openshift.restclient.ClientBuilder.withMaxRequests(I)Lcom/openshift/restclient/ClientBuilder;
> 	at org.jboss.tools.openshift.core.connection.ConnectionFactory.create(ConnectionFactory.java:53)
> 	at org.jboss.tools.openshift.core.connection.ConnectionFactory.create(ConnectionFactory.java:1)
> 	at org.jboss.tools.openshift.cdk.server.core.internal.listeners.CDKOpenshiftUtility.createOpenshiftConnection(CDKOpenshiftUtility.java:77)
> 	at org.jboss.tools.openshift.cdk.server.core.internal.listeners.CDKOpenshiftUtility.createOpenshiftConnection(CDKOpenshiftUtility.java:55)
> 	at org.jboss.tools.openshift.cdk.server.core.internal.listeners.ConfigureDependentFrameworksListener.configureOpenshift(ConfigureDependentFrameworksListener.java:91)
> 	at org.jboss.tools.openshift.cdk.server.core.internal.listeners.ConfigureDependentFrameworksListener.configureFrameworks(ConfigureDependentFrameworksListener.java:56)
> 	at org.jboss.tools.openshift.cdk.server.core.internal.listeners.ConfigureDependentFrameworksListener$1.run(ConfigureDependentFrameworksListener.java:44)
> 	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55){code}



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)


More information about the jbosstools-issues mailing list