[jbosstools-issues] [JBoss JIRA] (JBIDE-24230) CDK3 server adapter: duplicate server adapter path is created upon startup

[Martin Malina (JIRA)]

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

Martin Malina commented on JBIDE-24230:
---------------------------------------

[~rob.stryker], please clarify?
{quote}
If a new one is discovered but has a DIFFERENT minishift path declared, then we'll mark it as new.
{quote}
Different than what? For me, the cdk 3 server adapter that is created automatically via runtime detection does not have any minishift binary path set up. Which seems logical to me, because there is no way the runtime detection can learn the path.
So I verified the first use case - when you have this automatic server adapter and change it a bit and then restart your workspace, no new server will be created.
But I'm not sure what is the circumstance where a new server would actually be created if you already have a cdk3 server present.

Also, as to Andre's second use case:
{quote}
ASSERT: have a cdk3 server adapter
EXEC: delete it
EXEC: restart Eclipse
{quote}
There is no way to avoid this, right? As long as runtime detection finds something in ~/.minishift, it will always create a server adapter when none is present. Right?

> CDK3 server adapter: duplicate server adapter path is created upon startup
> --------------------------------------------------------------------------
>
>                 Key: JBIDE-24230
>                 URL: https://issues.jboss.org/browse/JBIDE-24230
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: cdk
>    Affects Versions: 4.4.4.AM2
>            Reporter: Andre Dietisheim
>            Assignee: Rob Stryker
>             Fix For: 4.4.4.AM3
>
>         Attachments: cdk3 server adapter gets duplicated.mp4, cdk3 server adapter reappears.mp4
>
>




--
This message was sent by Atlassian JIRA
(v7.2.3#72005)