[JBoss JIRA] (TOOLSDOC-718) Getting Started / Readme for new CDK users
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-718?page=com.atlassian.jira.plug... ]
Alexey Kazakov edited comment on TOOLSDOC-718 at 4/17/16 10:29 AM:
-------------------------------------------------------------------
3) The installer passes the username only. You still need to re-enter your developers.redhat.password when starting CDK server adapter first time. You can save the password in that dialogue so you won't have to re-enter it every time you start the CDK.
6) There are two known issues which are worth mentioning IMO.
- JBIDE-21983 when you open Docker Explorer the very first time and then try to extend/unfold Containers or Images the explorer will fail and threw an exception. You have to restart Eclipse/JBDS to make it work.
- JBIDE-22186 when you started the CDK the very first time and then go to OpenShift explorer then you can use the automatically created connection right away. But if you stop the CDK and start it again then the openshift connection will ask you for the openshift password. It didn't save it when the connection was created. The default password you have to use here is "devel". You can save this password when you are being asked though.
So I think we should mention the default credentials in the doc that when user is asked for credentials when trying to expand an openshift connection in the openshift explorer.
was (Author: akazakov):
3) The installer passes the username only. You still need to re-enter your developers.redhat.password when starting CDK server adapter first time. You can save the password in that dialogue so you won't have to re-enter it every time you start the CDK.
6) There are two known issues which are worth mentioning IMO.
- when you open Docker Explorer the very first time and then try to extend/unfold Containers or Images the explorer will fail and threw an exception. You have to restart Eclipse/JBDS to make it work.
- when you started the CDK the very first time and then go to OpenShift explorer then you can use the automatically created connection right away. But if you stop the CDK and start it again then the openshift connection will ask you for the openshift password. It didn't save it when the connection was created. The default password you have to use here is "devel". You can save this password when you are being asked though.
So I think we should mention the default credentials in the doc that when user is asked for credentials when trying to expand an openshift connection in the openshift explorer.
> Getting Started / Readme for new CDK users
> -------------------------------------------
>
> Key: TOOLSDOC-718
> URL: https://issues.jboss.org/browse/TOOLSDOC-718
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Feature Request
> Components: General documentation issues
> Affects Versions: 9.1 CR1
> Reporter: Nick Boldt
> Assignee: Misha Ali
> Labels: Havoc
> Fix For: 9.1 GA
>
>
> See JBDS-3738.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (TOOLSDOC-718) Getting Started / Readme for new CDK users
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-718?page=com.atlassian.jira.plug... ]
Alexey Kazakov commented on TOOLSDOC-718:
-----------------------------------------
3) The installer passes the username only. You still need to re-enter your developers.redhat.password when starting CDK server adapter first time. You can save the password in that dialogue so you won't have to re-enter it every time you start the CDK.
6) There are two known issues which are worth mentioning IMO.
- when you open Docker Explorer the very first time and then try to extend/unfold Containers or Images the explorer will fail and threw an exception. You have to restart Eclipse/JBDS to make it work.
- when you started the CDK the very first time and then go to OpenShift explorer then you can use the automatically created connection right away. But if you stop the CDK and start it again then the openshift connection will ask you for the openshift password. It didn't save it when the connection was created. The default password you have to use here is "devel". You can save this password when you are being asked though.
So I think we should mention the default credentials in the doc that when user is asked for credentials when trying to expand an openshift connection in the openshift explorer.
> Getting Started / Readme for new CDK users
> -------------------------------------------
>
> Key: TOOLSDOC-718
> URL: https://issues.jboss.org/browse/TOOLSDOC-718
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Feature Request
> Components: General documentation issues
> Affects Versions: 9.1 CR1
> Reporter: Nick Boldt
> Assignee: Misha Ali
> Labels: Havoc
> Fix For: 9.1 GA
>
>
> See JBDS-3738.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-22185) [search results] provide a visual clue when resolution != resolved
by Marcel Bruch (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22185?page=com.atlassian.jira.plugi... ]
Marcel Bruch resolved JBIDE-22185.
----------------------------------
Fix Version/s: 4.3.1.Final
Resolution: Done
> [search results] provide a visual clue when resolution != resolved
> ------------------------------------------------------------------
>
> Key: JBIDE-22185
> URL: https://issues.jboss.org/browse/JBIDE-22185
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: aeri
> Affects Versions: 4.3.1.CR1
> Reporter: Fred Bricon
> Assignee: Marcel Bruch
> Priority: Minor
> Fix For: 4.3.1.Final
>
> Attachments: screenshot-1.png
>
>
> It'd be helpful if we had a visual clue the problems returned by the search in the Frontend are resolved/closed. For instance, by striking the Bug id.
> !http://content.screencast.com/users/fbricon/folders/Jing/media/d07e10f9-b1a8-4120-b419-fc09e0d3caf2/00000385.png|width=850!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (TOOLSDOC-700) JBDS 9.1 Beta2: Additional docker functionality
by Misha Ali (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-700?page=com.atlassian.jira.plug... ]
Misha Ali updated TOOLSDOC-700:
-------------------------------
Sprint: 18-Jan >> 31-Jan 2016-JBDS/JBT, 01-Feb >> 14-Feb 2016-JBDS/JBT, 15-Feb >> 28-Feb 2016-JBDS/JBT, 29-Feb >> 13-Mar 2016-JBDS/JBT, 14-Mar >> 27-Mar 2016-JBDS/J 2, 25-Apr >> 08-May 2016-JBDS/JBT (was: 18-Jan >> 31-Jan 2016-JBDS/JBT, 01-Feb >> 14-Feb 2016-JBDS/JBT, 15-Feb >> 28-Feb 2016-JBDS/JBT, 29-Feb >> 13-Mar 2016-JBDS/JBT, 14-Mar >> 27-Mar 2016-JBDS/J 2, 11-Apr >> 24-Apr 2016-JBDS/J 2)
> JBDS 9.1 Beta2: Additional docker functionality
> -----------------------------------------------
>
> Key: TOOLSDOC-700
> URL: https://issues.jboss.org/browse/TOOLSDOC-700
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Bug
> Components: General documentation issues
> Affects Versions: 9.1 Beta2
> Reporter: Misha Ali
> Assignee: Misha Ali
> Labels: Docker
>
> Docker (in 9.0.0, adding CDK target and usability improvements):
> - [Server Adapter to start/stop/restart/auto-configure the CDK's Vagrant VM|https://issues.jboss.org/browse/JBIDE-20153]
> - docker run
> - docker build
> - docker logs
> - run/build as launch configurations so users can rerun
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (TOOLSDOC-709) JBDS 9.1 GA: Document a use case for Forge Tooling
by Misha Ali (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-709?page=com.atlassian.jira.plug... ]
Misha Ali updated TOOLSDOC-709:
-------------------------------
Sprint: 01-Feb >> 14-Feb 2016-JBDS/JBT, 15-Feb >> 28-Feb 2016-JBDS/JBT, 29-Feb >> 13-Mar 2016-JBDS/JBT, 14-Mar >> 27-Mar 2016-JBDS/J 2, 28-Mar >> 10-Apr 2016-JBDS/JBT (was: 01-Feb >> 14-Feb 2016-JBDS/JBT, 15-Feb >> 28-Feb 2016-JBDS/JBT, 29-Feb >> 13-Mar 2016-JBDS/JBT, 14-Mar >> 27-Mar 2016-JBDS/J 2, 28-Mar >> 10-Apr 2016-JBDS/JBT, 11-Apr >> 24-Apr 2016-JBDS/J 2)
> JBDS 9.1 GA: Document a use case for Forge Tooling
> --------------------------------------------------
>
> Key: TOOLSDOC-709
> URL: https://issues.jboss.org/browse/TOOLSDOC-709
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Enhancement
> Components: General documentation issues
> Affects Versions: 9.1 GA
> Reporter: Misha Ali
> Assignee: Supriya Bharadwaj
> Labels: Forge
> Fix For: 9.1 GA
>
>
> Document a use case for Forge tooling.
> 1. Draft a potential use case for what users may want to do with forge.
> 2. Get review on use case idea from a relevant SME or QE person
> 3. Write an intro and flesh out the use case with relevant screenshots
> 4. Get QE review
> 5. Create upstream and downstream versions of approved content.
> a. Add CSP version to customer portal
> b. Send Misha upstream version
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years