[jbosstools-issues] [JBoss JIRA] (JBIDE-21173) Runtime detection not working for CDK 2 Beta3

Rob Stryker (JIRA) issues at jboss.org
Wed Dec 2 20:35:00 EST 2015


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

Rob Stryker commented on JBIDE-21173:
-------------------------------------

I'll leave the issue open for now, but I don't expect any coding changes here.  There's pretty much no way to tell a CDK Vagrantfile from any random vagrant file that has nothing to do with cdk.  The .cdk marker is the way we've decided how to detect the cdk, and we're working to ensure that the jbds installer has the marker.  Fred's idea to get the openshift-vagrant repo to also include the marker is also a great help. 

> Runtime detection not working for CDK 2 Beta3
> ---------------------------------------------
>
>                 Key: JBIDE-21173
>                 URL: https://issues.jboss.org/browse/JBIDE-21173
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: openshift
>    Affects Versions: 4.3.1.Beta1
>            Reporter: Martin Malina
>            Assignee: Rob Stryker
>
> When I point runtime detection to my cdk folder, it will not detect anything.
> I had the openshift.cdk feature installed.
> {code}
> nattura:features rasp$ ls|grep cdk
> org.jboss.tools.openshift.cdk.feature_3.1.0.Beta1-v20151202-0847-B100
> {code}
> And the runtime detection preference page shows that it will search for cdk runtimes 
> (CDK is checked).
> The cdk in the folder that I use work fine when I add the adapter manually.



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


More information about the jbosstools-issues mailing list