[JBoss JIRA] (JBIDE-22639) Opening an Openshift3 server adapter when connection does not exists anymore causes NPE
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22639?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich commented on JBIDE-22639:
-----------------------------------------------
This error is thrown by VariablesHelper.replaceVariables while retrieving OpenShiftServerUtils.getSourcePath(server); That may be an independent issue, connection might exist but project jboss-eap-quickstarts be unavailable. [~adietish], can we throw a specific exception in VariablesHelper.replaceVariables to be caught here and shown in a user friendly way?
> Opening an Openshift3 server adapter when connection does not exists anymore causes NPE
> ---------------------------------------------------------------------------------------
>
> Key: JBIDE-22639
> URL: https://issues.jboss.org/browse/JBIDE-22639
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift, server
> Affects Versions: 4.4.0.Final
> Reporter: Jeff MAURY
> Fix For: 4.4.1.M2
>
> Attachments: non-existent-workspace-reference.png, screenshot-1.png
>
>
> ASSERT: create an Openshift3 connection
> ASSERT: create a server adapter from that connection
> ASSERT: delete the Openshift3 connection
> EXEC: open the server adapter
> ASSERT: NPE is thrown and dialog is displayed (see [^screenshot-1.png])
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBDS-3282) Screencasts: OpenShift v3
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBDS-3282?page=com.atlassian.jira.plugin.... ]
Fred Bricon commented on JBDS-3282:
-----------------------------------
New screencast showcasing docker deployment on the cdk: https://www.youtube.com/watch?v=BnUz2TuL25M
> Screencasts: OpenShift v3
> -------------------------
>
> Key: JBDS-3282
> URL: https://issues.jboss.org/browse/JBDS-3282
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Feature Request
> Components: documentation, openshift, requirements
> Reporter: Burr Sutter
> Assignee: Fred Bricon
> Priority: Critical
> Labels: screencast
> Fix For: 10.0.1.M1
>
>
> A series of short (5 minutes), educational videos to illustrate the new capabilities of JBDS associated with OpenShift.
> Including:
> - OpenShift's new web UI
> - OpenShift Explorer in the context of v3
> - perhaps an overview of Kubernetes, depends on how "pods" become visible to our end-user
> - an overview of Docker, depends on how 'containers" become visible to our end-user
> and all the typical start, stop, add, delete/remove, view logs, set env vars, etc.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBIDE-21205) Modify runtime detection to ensure a detector is only asked to initialize runtime definitions it created
by Radim Hopp (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21205?page=com.atlassian.jira.plugi... ]
Radim Hopp closed JBIDE-21205.
------------------------------
> Modify runtime detection to ensure a detector is only asked to initialize runtime definitions it created
> --------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-21205
> URL: https://issues.jboss.org/browse/JBIDE-21205
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: runtime-detection
> Affects Versions: 4.3.0.Beta2
> Reporter: Rob Stryker
> Assignee: Rob Stryker
> Priority: Minor
> Fix For: 4.4.0.Alpha1
>
>
> See https://issues.jboss.org/browse/JBIDE-21193 for some background.
> A runtime detector is asked to initialize all RuntimeDefinition objects, not just ones it created. While this "works" if you expect a detector to know all type-strings that it creates RuntimeDefinition objects using, it is still less than optimal and the workflow is a bit counter-intuitive.
> Suggestion is to add a new constructor to RuntimeDefinition and add abstract method for creating those definitions to AbstractRuntimeDetectorDelegate to instantiate these definitions.
> Care should be taken since this is all public API and used in Fuse, cdk, servertools, and other locations. It may not be possible to compel consumers to use the new API at all, and so the benefit may be zero.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBTIS-797) Use parametrized tests in ConfigurationsEditorTest
by Andrej Podhradsky (JIRA)
Andrej Podhradsky created JBTIS-797:
---------------------------------------
Summary: Use parametrized tests in ConfigurationsEditorTest
Key: JBTIS-797
URL: https://issues.jboss.org/browse/JBTIS-797
Project: JBoss Tools Integration Stack
Issue Type: Task
Components: Fuse IDE, QE
Affects Versions: 4.3.0.Final
Reporter: Andrej Podhradsky
Assignee: Dominik Jelinek
Fix For: 4.3.1.Final
Use parameterized tests in ConfigurationsEditorTest
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (ERT-324) Allow to tag image with --force [EBZ#496921]
by Friendly Jira Robot (JIRA)
Friendly Jira Robot created ERT-324:
---------------------------------------
Summary: Allow to tag image with --force [EBZ#496921]
Key: ERT-324
URL: https://issues.jboss.org/browse/ERT-324
Project: Eclipse Release Train
Issue Type: Task
Components: Linux Tools
Reporter: Friendly Jira Robot
Fix For: Neon.1 (4.6)
The dialog to tag an image should propose the '--force' flag.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months