March 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (ERT-74) JSON Editor feature is uncategorized in the update site [EBZ#487038]

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/ERT-74?page=com.atlassian.jira.plugin.sys... ] Max Rydahl Andersen updated ERT-74: ----------------------------------- Sprint: devex #3 February 2016, devex #4 March 2016 (was: devex #3 February 2016) > JSON Editor feature is uncategorized in the update site [EBZ#487038] > -------------------------------------------------------------------- > > Key: ERT-74 > URL: https://issues.jboss.org/browse/ERT-74 > Project: Eclipse Release Train > Issue Type: Task > Components: WTP Releng > Reporter: Friendly Jira Robot > Assignee: Victor Rubezhny > Labels: bzira, wst.json > > The JSON Editor feature can not be found under http://download.eclipse.org/webtools/downloads/drops/R3.8.0/S-3.8.0M5-201..., unless "Group items by category" is unchecked. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21625) Server adapter: Enable debug mode on OpenShift servers

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21625?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-21625: ---------------------------------------- Sprint: devex #2 February 2016, devex #3 February 2016, devex #4 March 2016 (was: devex #2 February 2016, devex #3 February 2016) > Server adapter: Enable debug mode on OpenShift servers > ------------------------------------------------------ > > Key: JBIDE-21625 > URL: https://issues.jboss.org/browse/JBIDE-21625 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Reporter: Fred Bricon > Assignee: Fred Bricon > Priority: Critical > Labels: openshift_v3, server_adapter > Fix For: 4.3.1.CR1 > > > Need to easily enable debug mode on EAP/Node images. That should allow hot reloading of server.js or java classes -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21719) Move Properties view to its previous position

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21719?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-21719: -------------------------------------- Assignee: Viacheslav Kabanovich > 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 > Assignee: Viacheslav Kabanovich > 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
0
0 / 0

[JBoss JIRA] (JBIDE-21719) Move Properties view to its previous position

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21719?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-21719: ---------------------------------------- {quote}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.{quote} I like this idea. So it will look like on this screenshot? !JBossPerspective_PropertiesMayBeWider.png|thumbnail! I'm voting +1 to the proposed PR (need to be tested though, cc: [~ldimaggio]), [~maxandersen] WDYT? > 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
0
0 / 0

[JBoss JIRA] (JBDS-3626) Error message about not signed T&C agreement should give users info how to sign it

by Josephine Qian (JIRA)

[ https://issues.jboss.org/browse/JBDS-3626?page=com.atlassian.jira.plugin.... ] Josephine Qian commented on JBDS-3626: -------------------------------------- I am not sure how I can help with this issue. Can you give me more info if I am needed here? > Error message about not signed T&C agreement should give users info how to sign it > ---------------------------------------------------------------------------------- > > Key: JBDS-3626 > URL: https://issues.jboss.org/browse/JBDS-3626 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Reporter: Alexey Kazakov > Assignee: Joshua Wilson > Priority: Blocker > Labels: havoc, ui > Fix For: 9.1.0.CR1 > > Attachments: You_re_almost_there___Red_Hat_Developers.png > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21867) Openshift does not provide any log messages from the rest client when trace is enabled

by Jeff Cantrill (JIRA)

Jeff Cantrill created JBIDE-21867: ------------------------------------- Summary: Openshift does not provide any log messages from the rest client when trace is enabled Key: JBIDE-21867 URL: https://issues.jboss.org/browse/JBIDE-21867 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.3.1.Beta2 Reporter: Jeff Cantrill Priority: Minor Enabling trace does not provide any rest client log messages. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21867) Openshift does not provide any log messages from the rest client when trace is enabled

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21867?page=com.atlassian.jira.plugi... ] Jeff Cantrill reassigned JBIDE-21867: ------------------------------------- Assignee: Jeff Cantrill > Openshift does not provide any log messages from the rest client when trace is enabled > -------------------------------------------------------------------------------------- > > Key: JBIDE-21867 > URL: https://issues.jboss.org/browse/JBIDE-21867 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Priority: Minor > > Enabling trace does not provide any rest client log messages. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21863) WatchManager makes multiple callbacks for same event

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21863?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich edited comment on JBIDE-21863 at 3/14/16 4:50 PM: ------------------------------------------------------------------------ When WatchManager.stopWatch is called in the context of DeploymentResourceMapper.buildDeployments(), it seems buildDeployments() does not want that watch for this project be restarted until it explicitly calls in finally block WatchManager.getInstance().startWatch(project). So, maybe in this context a flag may be set on WatchManager and calls to WatchListener for the project may be just ignored until buildDeployments() explicitly restarts the watch and remove the flag? was (Author: scabanovich): When WatchManager.stopWatch is called in the context of DeploymentResourceMapper.buildDeployments(), it seems buildDeployments(project) does not want that watch for this project be restarted until it explicitly calls in finally block WatchManager.getInstance().startWatch(project). So, maybe in this context a flag may be set on WatchManager and calls to WatchListener for the project may be just ignored until buildDeployments() explicitly restarts the watch and remove the flag? > WatchManager makes multiple callbacks for same event > ---------------------------------------------------- > > Key: JBIDE-21863 > URL: https://issues.jboss.org/browse/JBIDE-21863 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Priority: Blocker > Fix For: 4.4.0.Alpha1 > > > There is an issue in either the WatchClient or the the dependent functionality of the the openshift-rest-client where a new listener is registered when the watch restarts from a timeout. Listeners should only be able registered once -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3631) When an install fails, the user is able to view the error log to debug the cause of the failure, but the UI does not display any details

by Josephine Qian (JIRA)

[ https://issues.jboss.org/browse/JBDS-3631?page=com.atlassian.jira.plugin.... ] Josephine Qian commented on JBDS-3631: -------------------------------------- Please see the recommendation in this issue: https://issues.jboss.org/browse/JBDS-3622 > When an install fails, the user is able to view the error log to debug the cause of the failure, but the UI does not display any details > ---------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBDS-3631 > URL: https://issues.jboss.org/browse/JBDS-3631 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Components: installer > Reporter: Len DiMaggio > Assignee: Joshua Wilson > Labels: havoc, ui > Fix For: 9.1.0.CR1 > > Attachments: install_error.png > > > It would be helpful to provide the user either a summary of the last failure, or a window that displays the install log, inside the installer UI. Thx! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21863) WatchManager makes multiple callbacks for same event

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21863?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich commented on JBIDE-21863: ----------------------------------------------- When WatchManager.stopWatch is called in the context of DeploymentResourceMapper.buildDeployments(), it seems buildDeployments(project) does not want that watch for this project be restarted until it explicitly calls in finally block WatchManager.getInstance().startWatch(project). So, maybe in this context a flag may be set on WatchManager and calls to WatchListener for the project may be just ignored until buildDeployments() explicitly restarts the watch and remove the flag? > WatchManager makes multiple callbacks for same event > ---------------------------------------------------- > > Key: JBIDE-21863 > URL: https://issues.jboss.org/browse/JBIDE-21863 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Priority: Blocker > Fix For: 4.4.0.Alpha1 > > > There is an issue in either the WatchClient or the the dependent functionality of the the openshift-rest-client where a new listener is registered when the watch restarts from a timeout. Listeners should only be able registered once -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues March 2016