[JBoss JIRA] (JBDS-3566) include AERI in JBDS 9.1
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3566?page=com.atlassian.jira.plugin.... ]
Nick Boldt edited comment on JBDS-3566 at 3/11/16 6:00 PM:
-----------------------------------------------------------
Reopening. I can't make Aeri work in JBDS 9.1.0.CR1.
I've created a dummy aeri-discovery site here:
https://devstudio.jboss.com/9.0/aeri-discovery/
I've tried installation of jboss-devstudio-9.1.0.CR1-v20160311-1249-B402-installer-standalone.jar against a fresh workspace, then launching it thus:
{code}./jbdevstudio -Dorg.eclipse.recommenders.stacktraces.rcp.serverUrl=https://devstudio.jboss.com/9.0/aeri-discovery{code}
Also tried adding the -D flag directly into the jbdevstudio.ini file. In both cases, I get this when I go to Window > Prefs > General > Error Reporting > Configure Projects...
!aeri-in-jbds91.png!
But I can't get the AERI reporting to fire when I cause problem in p2, as suggested above.
was (Author: nickboldt):
Reopening. I can't make Aeri work in JBDS 9.1.0.CR1.
I've created a dummy aeri-discovery site here:
https://devstudio.jboss.com/9.0/aeri-discovery/
I've tried installation of jboss-devstudio-9.1.0.CR1-v20160311-1249-B402-installer-standalone.jar against a fresh workspace, then launching it thus:
{code}./jbdevstudio -Dorg.eclipse.recommenders.stacktraces.rcp.serverUrl=https://devstudio.jboss.com/9.0/aeri-discovery{code}
Also tried adding the -D flag directly into the jbdevstudio.ini file. In both cases, I get this when I go to Window > Prefs > General > Error Reporting > Configure Projects...
!!
But I can't get the AERI reporting to fire when I cause problem in p2, as suggested above.
> include AERI in JBDS 9.1
> ------------------------
>
> Key: JBDS-3566
> URL: https://issues.jboss.org/browse/JBDS-3566
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: aeri, build, target-platform
> Affects Versions: 9.1.0.Beta1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Blocker
> Attachments: aeri-in-jbds91.png, error-prefs-jbds.png, error-prefs-jbt.png, error-reporting.png
>
>
> Include required bundles for AERI in JBDS. Details TBD.
> Maybe need these?
> {code}
> org.eclipse.epp.logging.aeri.feature_1.0.1.v20150913-0716
> org.eclipse.epp.logging.aeri.ide_1.0.1.v20150913-0657.jar
> org.eclipse.epp.logging.aeri.ui_1.0.1.v20150913-0716.jar
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBDS-3566) include AERI in JBDS 9.1
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3566?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-3566:
-----------------------------
Attachment: aeri-in-jbds91.png
> include AERI in JBDS 9.1
> ------------------------
>
> Key: JBDS-3566
> URL: https://issues.jboss.org/browse/JBDS-3566
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: aeri, build, target-platform
> Affects Versions: 9.1.0.Beta1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Blocker
> Attachments: aeri-in-jbds91.png, error-prefs-jbds.png, error-prefs-jbt.png, error-reporting.png
>
>
> Include required bundles for AERI in JBDS. Details TBD.
> Maybe need these?
> {code}
> org.eclipse.epp.logging.aeri.feature_1.0.1.v20150913-0716
> org.eclipse.epp.logging.aeri.ide_1.0.1.v20150913-0657.jar
> org.eclipse.epp.logging.aeri.ui_1.0.1.v20150913-0716.jar
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21719) Move Properties view to its previous position
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21719?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich commented on JBIDE-21719:
-----------------------------------------------
I attached the pull request which implements:
- views not explicitly assigned to a folder in JBoss perspective, are collected from extensions and assigned to middle lower part;
- default width of right lower part is increased to make more space for Properties view and to let user see that he can adjust it without changing editor area.
[~maxandersen], please review the pull request.
> Move Properties view to its previous position
> ---------------------------------------------
>
> Key: JBIDE-21719
> URL: https://issues.jboss.org/browse/JBIDE-21719
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: common/jst/core
> Affects Versions: 4.3.1.Beta2
> Environment: JBDS 9.1.0.Beta2
> JBDS 9.1.0.CR1-v20160218-0332-B322 (nightly build)
> Reporter: Andrej Podhradsky
> Priority: Minor
> Fix For: 4.3.1.CR1
>
> Attachments: jbds-8.1.0.GA.png, jbds-9.1.0.CR1.png, jbds910_narrow_properties_view.png, JBossPerspective_PropertiesMayBeWider.png
>
>
> I noticed that the Properties view is located at the right bottom (see the screenshot jbds-9.1.0.CR1.png). The width of the view is not enough if we want to use it in SwitchYard / Camel / BPMN2 editor. Please move it to the position as it was in JBDS 8.1.0.GA (jbds-8.1.0.GA.png).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21719) Move Properties view to its previous position
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21719?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich edited comment on JBIDE-21719 at 3/11/16 5:30 PM:
------------------------------------------------------------------------
I attached the pull request which implements:
- views not explicitly assigned to a folder in JBoss perspective, are collected from extensions and assigned to middle lower part;
- default width of right lower part is increased to make more space for Properties view and to let user see that he can adjust it without changing editor area.
[~maxandersen], please review the pull request.
was (Author: scabanovich):
I attached the pull request which implements:
- views not explicitly assigned to a folder in JBoss perspective, are collected from extensions and assigned to middle lower part;
- default width of right lower part is increased to make more space for Properties view and to let user see that he can adjust it without changing editor area.
[~maxandersen], please review the pull request.
> Move Properties view to its previous position
> ---------------------------------------------
>
> Key: JBIDE-21719
> URL: https://issues.jboss.org/browse/JBIDE-21719
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: common/jst/core
> Affects Versions: 4.3.1.Beta2
> Environment: JBDS 9.1.0.Beta2
> JBDS 9.1.0.CR1-v20160218-0332-B322 (nightly build)
> Reporter: Andrej Podhradsky
> Priority: Minor
> Fix For: 4.3.1.CR1
>
> Attachments: jbds-8.1.0.GA.png, jbds-9.1.0.CR1.png, jbds910_narrow_properties_view.png, JBossPerspective_PropertiesMayBeWider.png
>
>
> I noticed that the Properties view is located at the right bottom (see the screenshot jbds-9.1.0.CR1.png). The width of the view is not enough if we want to use it in SwitchYard / Camel / BPMN2 editor. Please move it to the position as it was in JBDS 8.1.0.GA (jbds-8.1.0.GA.png).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21847) Start port forwarding button is disabled after starting and stopping it
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21847?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich commented on JBIDE-21847:
-----------------------------------------------
I attached pull request that tries to solve the problem from the point of view that I described above.
[~mlabuda], do you have an opportunity to try it in your environment? If after message in console "Stopping port-forwarding..." you will see a message "Waiting for port-forwarding to stop..." then indeed the thread had to wait until ports get free.
> Start port forwarding button is disabled after starting and stopping it
> -----------------------------------------------------------------------
>
> Key: JBIDE-21847
> URL: https://issues.jboss.org/browse/JBIDE-21847
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Assignee: Snjezana Peco
> Labels: openshift_v3, port_forwarding_wizard
> Fix For: 4.3.1.CR1
>
> Attachments: video.ogg-2.ogv
>
>
> In Port Forwarding wizard when I start port forwarding, then stop it, the button Start All is disabled and it is not possible to start port forwarding again. Well, both buttons after starting and stopping are disabled, only OK is enabled.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21831) Change host to localhost when cdk is selected in new server dialog
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21831?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-21831:
-----------------------------------
Fix Version/s: 4.4.0.Alpha1
(was: 4.3.1.CR1)
> Change host to localhost when cdk is selected in new server dialog
> ------------------------------------------------------------------
>
> Key: JBIDE-21831
> URL: https://issues.jboss.org/browse/JBIDE-21831
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk
> Affects Versions: 4.3.1.CR1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Priority: Minor
> Fix For: 4.4.0.Alpha1
>
>
> When you open the new server dialog, select OpenShift 2, it will set host to openshift.redhat.com. When you then select cdk, it will complain that it only works on localhost. So the suggestion is to make it work the same way OpenShift adapters work and ensure that host is always changed to localhost when you select the cdk adapter.
> This was spotted and brought up by [~mlabuda].
> For reference, this is the JIRA where similar thing was discussed for OpenShift: JBIDE-20114
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21831) Change host to localhost when cdk is selected in new server dialog
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21831?page=com.atlassian.jira.plugi... ]
Alexey Kazakov commented on JBIDE-21831:
----------------------------------------
Moved to 4.4 since it doesn't look like a blocker.
> Change host to localhost when cdk is selected in new server dialog
> ------------------------------------------------------------------
>
> Key: JBIDE-21831
> URL: https://issues.jboss.org/browse/JBIDE-21831
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk
> Affects Versions: 4.3.1.CR1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Priority: Minor
> Fix For: 4.4.0.Alpha1
>
>
> When you open the new server dialog, select OpenShift 2, it will set host to openshift.redhat.com. When you then select cdk, it will complain that it only works on localhost. So the suggestion is to make it work the same way OpenShift adapters work and ensure that host is always changed to localhost when you select the cdk adapter.
> This was spotted and brought up by [~mlabuda].
> For reference, this is the JIRA where similar thing was discussed for OpenShift: JBIDE-20114
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21439) Add JSON Editor to JBDS/JBT Target Platform
by Victor Rubezhny (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21439?page=com.atlassian.jira.plugi... ]
Victor Rubezhny commented on JBIDE-21439:
-----------------------------------------
[~nickboldt] I would wait for m6 because it contains partial fix for ERT-76
> Add JSON Editor to JBDS/JBT Target Platform
> -------------------------------------------
>
> Key: JBIDE-21439
> URL: https://issues.jboss.org/browse/JBIDE-21439
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: target-platform
> Reporter: Alexey Kazakov
> Assignee: Nick Boldt
> Priority: Critical
> Fix For: 4.4.0.Alpha1
>
>
> Missing description. Need update site from which to fetch IUs, and a list of which IUs to add.
> Also need to know what to do with the JSON editor once it's in the TP... will it be installed OOTB like YAML editor in JBIDE-21377? Or will it be a new Central connector?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBIDE-21439) Add JSON Editor to JBDS/JBT Target Platform
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21439?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-21439:
------------------------------------
[~vrubezhny] Did this get into M5? Or should we wait until M6 in two weeks?
> Add JSON Editor to JBDS/JBT Target Platform
> -------------------------------------------
>
> Key: JBIDE-21439
> URL: https://issues.jboss.org/browse/JBIDE-21439
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: target-platform
> Reporter: Alexey Kazakov
> Assignee: Nick Boldt
> Priority: Critical
> Fix For: 4.4.0.Alpha1
>
>
> Missing description. Need update site from which to fetch IUs, and a list of which IUs to add.
> Also need to know what to do with the JSON editor once it's in the TP... will it be installed OOTB like YAML editor in JBIDE-21377? Or will it be a new Central connector?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month