[JBoss JIRA] (TOOLSDOC-702) JBDS-IS 8.0.4: Update Components and Supported Configurations
by Misha Ali (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-702?page=com.atlassian.jira.plug... ]
Misha Ali updated TOOLSDOC-702:
-------------------------------
Labels: Support (was: )
> JBDS-IS 8.0.4: Update Components and Supported Configurations
> -------------------------------------------------------------
>
> Key: TOOLSDOC-702
> URL: https://issues.jboss.org/browse/TOOLSDOC-702
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Task
> Components: General documentation issues
> Affects Versions: 8.0.4
> Reporter: Andrej Podhradsky
> Assignee: Misha Ali
> Priority: Blocker
> Labels: Support
> Fix For: 8.0.4
>
>
> The documentation "Red Hat JBoss Developer Studio Integration Stack Components and Supported Configurations" on CSP doesn't contain info about JBDS-IS 8.0.4 (the latest info is about 8.0.3).
> Please update the list of released components as follows
> Teiid Designer 9.0.4.Final
> ModeShape 3.7.0.Final
> jBPM3 4.5.200.Final
> BPEL 1.3.100.Final_1.0.5.Final
> BPMN2 1.1.3.Final
> Drools 6.2.0.Final
> ESB 1.5.530.Final
> SwitchYard 2.0.1.Final
> Fuse Tooling 7.3.2.Final
> Note: The list of Early Access Components is empty (SwitchYard and fuse tooling was moved from EA to GA)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (TOOLSDOC-702) JBDS-IS 8.0.4: Update Components and Supported Configurations
by Misha Ali (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-702?page=com.atlassian.jira.plug... ]
Misha Ali updated TOOLSDOC-702:
-------------------------------
Sprint: 04-Jan >> 17-Jan 2016-JBDS/JBT
> JBDS-IS 8.0.4: Update Components and Supported Configurations
> -------------------------------------------------------------
>
> Key: TOOLSDOC-702
> URL: https://issues.jboss.org/browse/TOOLSDOC-702
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Task
> Components: General documentation issues
> Affects Versions: 8.0.4
> Reporter: Andrej Podhradsky
> Assignee: Misha Ali
> Priority: Blocker
> Labels: Support
> Fix For: 8.0.4
>
>
> The documentation "Red Hat JBoss Developer Studio Integration Stack Components and Supported Configurations" on CSP doesn't contain info about JBDS-IS 8.0.4 (the latest info is about 8.0.3).
> Please update the list of released components as follows
> Teiid Designer 9.0.4.Final
> ModeShape 3.7.0.Final
> jBPM3 4.5.200.Final
> BPEL 1.3.100.Final_1.0.5.Final
> BPMN2 1.1.3.Final
> Drools 6.2.0.Final
> ESB 1.5.530.Final
> SwitchYard 2.0.1.Final
> Fuse Tooling 7.3.2.Final
> Note: The list of Early Access Components is empty (SwitchYard and fuse tooling was moved from EA to GA)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (TOOLSDOC-702) JBDS-IS 8.0.4: Update Components and Supported Configurations
by Misha Ali (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-702?page=com.atlassian.jira.plug... ]
Misha Ali commented on TOOLSDOC-702:
------------------------------------
Thanks for logging this issue, [~apodhrad]. I've updated the document here:
https://access.redhat.com/articles/1351903
Please have a look and confirm that it is now OK.
> JBDS-IS 8.0.4: Update Components and Supported Configurations
> -------------------------------------------------------------
>
> Key: TOOLSDOC-702
> URL: https://issues.jboss.org/browse/TOOLSDOC-702
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Task
> Components: General documentation issues
> Affects Versions: 8.0.4
> Reporter: Andrej Podhradsky
> Assignee: Misha Ali
> Priority: Blocker
> Fix For: 8.0.4
>
>
> The documentation "Red Hat JBoss Developer Studio Integration Stack Components and Supported Configurations" on CSP doesn't contain info about JBDS-IS 8.0.4 (the latest info is about 8.0.3).
> Please update the list of released components as follows
> Teiid Designer 9.0.4.Final
> ModeShape 3.7.0.Final
> jBPM3 4.5.200.Final
> BPEL 1.3.100.Final_1.0.5.Final
> BPMN2 1.1.3.Final
> Drools 6.2.0.Final
> ESB 1.5.530.Final
> SwitchYard 2.0.1.Final
> Fuse Tooling 7.3.2.Final
> Note: The list of Early Access Components is empty (SwitchYard and fuse tooling was moved from EA to GA)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-21356) Make OpenShift 3 resource edition more robust
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21356?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-21356:
--------------------------------
Fix Version/s: 4.3.1.CR1
(was: 4.3.1.Beta2)
> Make OpenShift 3 resource edition more robust
> ---------------------------------------------
>
> Key: JBIDE-21356
> URL: https://issues.jboss.org/browse/JBIDE-21356
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.3.0.Beta1
> Reporter: Fred Bricon
> Fix For: 4.3.1.CR1
>
>
> Following [~scabanovich]'s comment in JBIDE-20761:
> {quote}
> My concern is that the default editor is called if it is set for .json without a fallback for a case of failure of that unknown editor. We cannot be sure what editor a user may have set to be default for .json. That editor may be expecting some specific instance of editor input object and fail on what is provided. As it is, then json will not be opened at all, neither fancy nor plain text. However, if it is just temporal, till the expected contribution to jsdt, and that editor is going to be hardcoded to be opened, then no problem.
> {quote}
> Until we can rely on Eclipse's upcoming JSON editor (in Neon), we should try to harden editor detection/opening
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-21143) Triggering action on one connection refresh whole OpenShift Explorer view
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21143?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-21143:
--------------------------------
Fix Version/s: 4.3.1.CR1
(was: 4.3.1.Beta2)
> Triggering action on one connection refresh whole OpenShift Explorer view
> -------------------------------------------------------------------------
>
> Key: JBIDE-21143
> URL: https://issues.jboss.org/browse/JBIDE-21143
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta1
> Reporter: Marián Labuda
> Labels: explorer
> Fix For: 4.3.1.CR1
>
>
> Actions such as deleting or creating a new project for an OpenShift connection (those which change content of OpenShift Explorer visually) causes refreshing all connection in OpenShift Explorer view - I have spotted it when I was creating a project for a connection of local OpenShift instance and while this project was being shown in OpenShift Explorer view under the connection, a connection to internal OSE instance had been refreshed too and loading tree item was shown underneath.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-20716) Connection wizard: Switch from OpenShift 3 server type to OpenShift 2 in New Connection dialog trigger usage of default server
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20716?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-20716:
--------------------------------
Fix Version/s: 4.3.1.CR1
(was: 4.3.1.Beta2)
> Connection wizard: Switch from OpenShift 3 server type to OpenShift 2 in New Connection dialog trigger usage of default server
> ------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-20716
> URL: https://issues.jboss.org/browse/JBIDE-20716
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.3.0.CR1
> Reporter: Marián Labuda
> Priority: Minor
> Labels: connection_wizard
> Fix For: 4.3.1.CR1
>
>
> In a New Connection dialog if OpenShift 3 server type is selected and there is no server URL then switch to OpenShift 2 server type checks (enables) the Use default Server checkbox. We should have consistent behavior in switching between OpenShift 2 and OpenShift 3. Because if there is a server URL for OpenShift X server type and I switch to OpenShift Y server type, the URL value persists and checkbox is not being checked.
> We should not check the Use default Server check box upon switching from OpenShift 3 to OpenShift 2 server type with empty URL.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-20998) Application wizard: Validation error description in Resource Labels page is cut off
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20998?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-20998:
--------------------------------
Fix Version/s: 4.3.1.CR1
(was: 4.3.1.Beta2)
> Application wizard: Validation error description in Resource Labels page is cut off
> -----------------------------------------------------------------------------------
>
> Key: JBIDE-20998
> URL: https://issues.jboss.org/browse/JBIDE-20998
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.0.Final
> Reporter: Marián Labuda
> Priority: Minor
> Labels: application_wizard, openshift_v3
> Fix For: 4.3.1.CR1
>
> Attachments: resource_label_complete.png, resource_label_incomplete.png
>
>
> In Resource Label dialog there is a validation error description about correct format of a label. But the validation error description is cut off. On first sight it does not look like like cut off, but after resizing a shell more text is showed. See following image of cut off description:
> !resource_label_incomplete.png!
> And following image contains full description after resizing to "long enough" width:
> !resource_label_complete.png!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months