[jbosstools-issues] [JBoss JIRA] (JBIDE-25167) CDK 3.2+ adapter is created automatically even if I have CDK 3.1.1 installed

Martin Malina (JIRA) issues at jboss.org
Wed Oct 11 03:17:00 EDT 2017


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

Martin Malina commented on JBIDE-25167:
---------------------------------------

It turns out that the calls the detector on paths like these:
/Users/rasp/jbossqa/cdk/cdk-3.1.0/
/Users/rasp/jbossqa/cdk/cdk-3.1.1/
...
I'm not really sure where it got those paths from.
But that's still not all. There are still several calls and validations of the same ~/.minishift directory. Obviously any other than the first time it will fail because it already exists. But it still seems redundant.

> CDK 3.2+ adapter is created automatically even if I have CDK 3.1.1 installed
> ----------------------------------------------------------------------------
>
>                 Key: JBIDE-25167
>                 URL: https://issues.jboss.org/browse/JBIDE-25167
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: cdk
>    Affects Versions: 4.5.1.AM3
>            Reporter: Martin Malina
>            Assignee: Rob Stryker
>            Priority: Critical
>
> I installed devstudio 11.1.0.AM3 B1225 and when I launched it there was a cdk server adapter already set up. That's completely normal. But what's wrong is that it's the new 3.2+ adapter whereas what I have actually installed in ~/.minishift is version 3.1.1.
> The runtime detection should be able to detect the version in ~/.minishift/cdk and return a match only if the version is compatible with the given adapter.
> [~jkopriva] says cdk 3.1.1 cannot be launched with cdk 3.2+ adapter. I cannot really check that myself because my server adapter doesn't have minishift binary set up by default and you validate the version in the server editor, so I can't use 3.1.1 with the 3.2+ adapter.



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)


More information about the jbosstools-issues mailing list