[JBoss JIRA] (JBIDE-22549) "Result" dialog enhancements
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22549?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-22549:
-------------------------------------
[~xcoulon] can you give more information as to what type of method you're invoking? The UI for displaying results is different based on the result type. Also, a complete workflow would be helpful for me, but the signature might be enough if I can find another similar method in wildfly / eap with such a result.
> "Result" dialog enhancements
> ----------------------------
>
> Key: JBIDE-22549
> URL: https://issues.jboss.org/browse/JBIDE-22549
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: jmx
> Affects Versions: 4.4.0.Final
> Reporter: Xavier Coulon
> Attachments: Screenshot 2016-06-07 11.35.28.png
>
>
> When executing a JMX remote operation, the "Result" dialog displays a single column that cannot be expanded, and the row content cannot be copied into the clipboard.
> See the attached screenshot for visual explanations.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBIDE-22548) Fix remaining CDK names inconsistencies
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22548?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-22548:
-----------------------------------
Priority: Blocker (was: Major)
> Fix remaining CDK names inconsistencies
> ---------------------------------------
>
> Key: JBIDE-22548
> URL: https://issues.jboss.org/browse/JBIDE-22548
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk
> Affects Versions: 4.4.0.Final
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Priority: Blocker
> Labels: respin-a
> Fix For: 4.4.0.Final
>
>
> This is a follow up of JBIDE-22431 . There are some remaining things to be fixed.
> 1. Alexey asked for the server adapter to be renamed to "Red Hat Container Development Kit" but it's now "Red Hat Container Development Kit Support". While it makes sense to have "Support" in the feature/plugin name, I don't think it makes sense for the server adapter type or the server name once it's created. So please drop the Support.
> 2. Runtime detection now uses the name of "Container Development Environment". This is inconsistent with creating the server adapter manually. Some time ago we tried to unify this - EAP now has the same names both when created via runtime detection or manually (default name). So if we really want to use the CDE thing (which I'm not a fan of, but whatever), I suggest we use this as the default name when creating a CDK adapter manually. But the adapter type should probably still be "Red Hat Container Development Kit" (no Support)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBIDE-22548) Fix remaining CDK names inconsistencies
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22548?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-22548:
-----------------------------------
Fix Version/s: 4.4.0.Final
> Fix remaining CDK names inconsistencies
> ---------------------------------------
>
> Key: JBIDE-22548
> URL: https://issues.jboss.org/browse/JBIDE-22548
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk
> Affects Versions: 4.4.0.Final
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Labels: respin-a
> Fix For: 4.4.0.Final
>
>
> This is a follow up of JBIDE-22431 . There are some remaining things to be fixed.
> 1. Alexey asked for the server adapter to be renamed to "Red Hat Container Development Kit" but it's now "Red Hat Container Development Kit Support". While it makes sense to have "Support" in the feature/plugin name, I don't think it makes sense for the server adapter type or the server name once it's created. So please drop the Support.
> 2. Runtime detection now uses the name of "Container Development Environment". This is inconsistent with creating the server adapter manually. Some time ago we tried to unify this - EAP now has the same names both when created via runtime detection or manually (default name). So if we really want to use the CDE thing (which I'm not a fan of, but whatever), I suggest we use this as the default name when creating a CDK adapter manually. But the adapter type should probably still be "Red Hat Container Development Kit" (no Support)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBIDE-22548) Fix remaining CDK names inconsistencies
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22548?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-22548:
-----------------------------------
Labels: respin-a (was: )
> Fix remaining CDK names inconsistencies
> ---------------------------------------
>
> Key: JBIDE-22548
> URL: https://issues.jboss.org/browse/JBIDE-22548
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk
> Affects Versions: 4.4.0.Final
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Labels: respin-a
> Fix For: 4.4.0.Final
>
>
> This is a follow up of JBIDE-22431 . There are some remaining things to be fixed.
> 1. Alexey asked for the server adapter to be renamed to "Red Hat Container Development Kit" but it's now "Red Hat Container Development Kit Support". While it makes sense to have "Support" in the feature/plugin name, I don't think it makes sense for the server adapter type or the server name once it's created. So please drop the Support.
> 2. Runtime detection now uses the name of "Container Development Environment". This is inconsistent with creating the server adapter manually. Some time ago we tried to unify this - EAP now has the same names both when created via runtime detection or manually (default name). So if we really want to use the CDE thing (which I'm not a fan of, but whatever), I suggest we use this as the default name when creating a CDK adapter manually. But the adapter type should probably still be "Red Hat Container Development Kit" (no Support)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBIDE-22544) Redudant error report in Devstudio's Problems View
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22544?page=com.atlassian.jira.plugi... ]
Alexey Kazakov reassigned JBIDE-22544:
--------------------------------------
Assignee: Victor Rubezhny (was: Viacheslav Kabanovich)
OK. Looks like a JSDT issue?
[~scabanovich] can you please create a bugzilla with details you posted above?
[~vrubezhny] can you take a look?
> Redudant error report in Devstudio's Problems View
> --------------------------------------------------
>
> Key: JBIDE-22544
> URL: https://issues.jboss.org/browse/JBIDE-22544
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: javascript, upstream
> Reporter: Ondrej Dockal
> Assignee: Victor Rubezhny
> Fix For: 4.4.x
>
> Attachments: org.jboss.tools.batch.ui.bot.test.editor.design.DesignChunkStepElementTest.createStep(7).png
>
>
> Some test fails on checking number of errors in Problems View in devstudio. There are duplicated error reports.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBDS-3924) Installation looks incomplete but is actually completed
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBDS-3924?page=com.atlassian.jira.plugin.... ]
Alexey Kazakov commented on JBDS-3924:
--------------------------------------
But if you click on Next then everything looks good and the installation is completed correctly, correct?
Does it happen all the time for you?
> Installation looks incomplete but is actually completed
> -------------------------------------------------------
>
> Key: JBDS-3924
> URL: https://issues.jboss.org/browse/JBDS-3924
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: installer
> Affects Versions: 10.0.0.GA
> Environment: Fedora 23
> Using devstudio-10.0.0.GA-v20160603-1025-B5510-installer-standalone.jar
> Reporter: Misha Ali
> Assignee: Denis Golovin
> Labels: install, installation, installer
> Fix For: 10.x
>
> Attachments: devstudio10install.png
>
>
> Running the standalone installer file starts the devstudio install as expected, but twice I have noticed that the Next button is available to click (indicating that the installation has completed) when the status shows that only 2/3 of the installation steps are concluded. (see screenshot for this screen).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months