[JBoss JIRA] (JBIDE-22004) Runtime detection unable to detect CDK
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22004?page=com.atlassian.jira.plugi... ]
Rob Stryker resolved JBIDE-22004.
---------------------------------
Fix Version/s: 4.4.2.AM2
(was: 4.4.x)
Resolution: Done
This is fixed in cdk nightly build.
> Runtime detection unable to detect CDK
> --------------------------------------
>
> Key: JBIDE-22004
> URL: https://issues.jboss.org/browse/JBIDE-22004
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: runtime-detection, upstream
> Affects Versions: 4.3.1.CR1
> Reporter: Radim Hopp
> Assignee: Hardy Ferentschik
> Fix For: 4.4.2.AM2
>
>
> Due to absency of ".cdk" file in official distribution of CDK (version 2.0.0.Beta5), runtime detection is unable to detect it.
> Installator probably adds that file during install, but shouldn't we support detection of "by-hand" downloaded CDK?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (JBIDE-22598) Support runtime detection for manual CDK install
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22598?page=com.atlassian.jira.plugi... ]
Rob Stryker resolved JBIDE-22598.
---------------------------------
Resolution: Done
Done
> Support runtime detection for manual CDK install
> ------------------------------------------------
>
> Key: JBIDE-22598
> URL: https://issues.jboss.org/browse/JBIDE-22598
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: cdk, runtime-detection
> Affects Versions: 4.4.0.Final
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.4.2.AM2
>
>
> Right now with CDK 2.1 when you have a manual cdk install (i.e. using cdk.zip and then adding the vagrant box yourself), there will be no .cdk marker, so Runtime Detection will not work.
> The only case where Runtime Detection will work is when you use the (as of now Windows-only) suite installer. At that point Runtime Detection will do its thing silently without you noticing.
> The way I see it there are two options:
> a) Create and upstream issue with CDK and ask them to include a basic .cdk in their zip
> b) Make the runtime detection work without .cdk
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (JBDS-4084) Provide documentation using the installed studio
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBDS-4084?page=com.atlassian.jira.plugin.... ]
Alexey Kazakov commented on JBDS-4084:
--------------------------------------
I think we still miss a good getting started doc for devstuidio that we could use as a tutorial for the next steps as soon as devsuite is installed. [~mhusnain], [~rkratky] am I missing something?
IMO we should create a chapter http://developers.redhat.com/products/devsuite/get-started/ which starts with the very first steps in Devstudio after devsuite installation. Then we can add a direct link to this chapter to the last page of the installer. It doesn't make sense to refer to the document which tells users how to download and install the installer when the installation is finished.
> Provide documentation using the installed studio
> ------------------------------------------------
>
> Key: JBDS-4084
> URL: https://issues.jboss.org/browse/JBDS-4084
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Enhancement
> Components: platform-installer
> Affects Versions: 10.1.0.GA
> Reporter: Aurélien Pupier
>
> when following the getting started http://developers.redhat.com/products/devsuite/get-started/
> at the ned it redirect to the "command-line" version to use Containers.
> it would be really better to provide tutorials to use the installed JBDS and the pre-configured CDK which is available in Servers view.
> Personal note: I wasn't able to find by myself how do it in the Studio, I'm representing a UI-lover end-user, I asked for help on Devsuite HipChat channel
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (JBIDE-22640) Server Adapter Editor: Update to Openshift server adapter is not saved
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22640?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-22640:
-------------------------------------
[~mlabuda] That would be an enhancement. THis was a one-line bug fix. If you wish to make that enhancement, please open a new bug.
> Server Adapter Editor: Update to Openshift server adapter is not saved
> ----------------------------------------------------------------------
>
> Key: JBIDE-22640
> URL: https://issues.jboss.org/browse/JBIDE-22640
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift, server
> Affects Versions: 4.4.0.Final, 4.4.1.Final
> Reporter: Jeff MAURY
> Assignee: Rob Stryker
> Labels: openshift_v3, server_adapter_editor
> Fix For: 4.4.2.AM2
>
>
> ASSERT: create an Openshift3 connection
> ASSERT: create a server adapter from that connection
> ASSERT: delete the Openshift3 connection
> EXEC: open the server adapter
> ASSERT: the connection filed is blank
> EXEC: using the dropdown change the connection
> ASSERT: the dirty flag of the server editor is not set
> EXEC: close the server editor
> EXEC: open the server editor again
> ASSERT: the connection field is still blank
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (JBIDE-22640) Server Adapter Editor: Update to Openshift server adapter is not saved
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22640?page=com.atlassian.jira.plugi... ]
Rob Stryker resolved JBIDE-22640.
---------------------------------
Resolution: Done
> Server Adapter Editor: Update to Openshift server adapter is not saved
> ----------------------------------------------------------------------
>
> Key: JBIDE-22640
> URL: https://issues.jboss.org/browse/JBIDE-22640
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift, server
> Affects Versions: 4.4.0.Final, 4.4.1.Final
> Reporter: Jeff MAURY
> Assignee: Rob Stryker
> Labels: openshift_v3, server_adapter_editor
> Fix For: 4.4.2.AM2
>
>
> ASSERT: create an Openshift3 connection
> ASSERT: create a server adapter from that connection
> ASSERT: delete the Openshift3 connection
> EXEC: open the server adapter
> ASSERT: the connection filed is blank
> EXEC: using the dropdown change the connection
> ASSERT: the dirty flag of the server editor is not set
> EXEC: close the server editor
> EXEC: open the server editor again
> ASSERT: the connection field is still blank
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months