February 2016 - jbosstools-issues

[JBoss JIRA] (JBIDE-21646) Ensure Quickstarts for EAP7 will be supported in JBoss Central

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21646?page=com.atlassian.jira.plugi... ] Fred Bricon resolved JBIDE-21646. --------------------------------- Resolution: Done Made some modifications in master / 4.3.x, assuming the EAP 7 quickstarts will follow the same tagging convention as previous EAP 6.x. > Ensure Quickstarts for EAP7 will be supported in JBoss Central > -------------------------------------------------------------- > > Key: JBIDE-21646 > URL: https://issues.jboss.org/browse/JBIDE-21646 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: central, project-examples > Affects Versions: 4.3.1.CR1 > Reporter: Fred Bricon > Assignee: Fred Bricon > Fix For: 4.3.1.CR1 > > > Ensure Quickstarts for EAP7 will be supported in JBoss Central. Need to be smart about https://github.com/jbosstools/jbosstools-central/blob/master/examples/plu... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21749) OpenShift Server Adapter creation Wizard does not fit in 13" screen

by Xavier Coulon (JIRA)

Xavier Coulon created JBIDE-21749: ------------------------------------- Summary: OpenShift Server Adapter creation Wizard does not fit in 13" screen Key: JBIDE-21749 URL: https://issues.jboss.org/browse/JBIDE-21749 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.3.1.Beta2 Reporter: Xavier Coulon Attachments: Screenshot 2016-02-23 18.55.52.png The Server settings page is too high for my 13" screen: the "default route" section is barely visible. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ERT-47) Translate breakpoints from .js files to Chromium/Node V8 JavaScript Engine [EBZ#486061]

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/ERT-47?page=com.atlassian.jira.plugin.sys... ] Ilya Buziuk reassigned ERT-47: ------------------------------ Assignee: Ilya Buziuk > Translate breakpoints from .js files to Chromium/Node V8 JavaScript Engine [EBZ#486061] > --------------------------------------------------------------------------------------- > > Key: ERT-47 > URL: https://issues.jboss.org/browse/ERT-47 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Max Rydahl Andersen > Assignee: Ilya Buziuk > Labels: Debug, bzira > > Current implementation in ChromeDevTools can map breakpoints from files in workspace to running VM. Problem is .js file editor from ChomeDevTools should be used to create breakpoints, because breakpoint annotation id used in mapping is different from breakpoint annotation id used in JSDT. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3601) No splash screen during JBDS 8.x startup on Windows

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3601?page=com.atlassian.jira.plugin.... ] Denis Golovin commented on JBDS-3601: ------------------------------------- The issue is probably with splash.bmp format, I'll check what is wrong with it. > No splash screen during JBDS 8.x startup on Windows > --------------------------------------------------- > > Key: JBDS-3601 > URL: https://issues.jboss.org/browse/JBDS-3601 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer, upstream > Affects Versions: 8.1.0.GA > Environment: WIndows 7 (RHEV VM) + Oracle JDK 7 > Reporter: Lyle Wang > Fix For: 8.x > > > After a typical installation, when trying to startup JBDS 8 / 8.1, there is no splash screen (and loading progress bar) before showing up the JBDS main window. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3601) No splash screen during JBDS 8.x startup on Windows

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3601?page=com.atlassian.jira.plugin.... ] Denis Golovin reassigned JBDS-3601: ----------------------------------- Assignee: Denis Golovin > No splash screen during JBDS 8.x startup on Windows > --------------------------------------------------- > > Key: JBDS-3601 > URL: https://issues.jboss.org/browse/JBDS-3601 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer, upstream > Affects Versions: 8.1.0.GA > Environment: WIndows 7 (RHEV VM) + Oracle JDK 7 > Reporter: Lyle Wang > Assignee: Denis Golovin > Fix For: 8.x > > > After a typical installation, when trying to startup JBDS 8 / 8.1, there is no splash screen (and loading progress bar) before showing up the JBDS main window. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21735) Hibernate 5.1 Support

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21735?page=com.atlassian.jira.plugi... ] Koen Aers updated JBIDE-21735: ------------------------------ Fix Version/s: 4.4.0.Alpha1 > Hibernate 5.1 Support > --------------------- > > Key: JBIDE-21735 > URL: https://issues.jboss.org/browse/JBIDE-21735 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: hibernate > Affects Versions: 4.3.1.Beta2 > Reporter: Koen Aers > Assignee: Koen Aers > Fix For: 4.4.0.Alpha1 > > > With the release of Hibernate Core 5.1, we need to integrate a runtime containing these libraries into JBoss Tools. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21678) New Connection wizard: Getting started info is not visible by default

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21678?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-21678. --------------------------------- Verified on nightly build of JBT with OpenShift tooling B190. > New Connection wizard: Getting started info is not visible by default > ---------------------------------------------------------------------- > > Key: JBIDE-21678 > URL: https://issues.jboss.org/browse/JBIDE-21678 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Viacheslav Kabanovich > Labels: connection_wizard, openshift_v2, openshift_v3 > Fix For: 4.3.1.CR1 > > Attachments: default_new_conn.png, rendered_new_conn.png > > > In opened New Connection wizard there is supposed to be getting started text leading to either sign in page for OpenShift 2 or to getting started content for OpenShift 3, but it it empty by default. Upon changing e.g. server type or checking/unchecking Use default server checkbox, the text appears. Resizing window does not fix the problem. This is also happening when editing an existing OpenShift 3 connection (via context menu of a connection). > See screenshot of fresh opened New Connection wizard: > !default_new_conn.png! > and after checkbox is (un)checked or server type is changed: > !rendered_new_conn.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-20731) Finish button in Import OpenShift Application wizard does nothing if repo is already cloned

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20731?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-20731. --------------------------------- Verified on nightly build of JBT with OpenShift tooling B190. > Finish button in Import OpenShift Application wizard does nothing if repo is already cloned > ------------------------------------------------------------------------------------------- > > Key: JBIDE-20731 > URL: https://issues.jboss.org/browse/JBIDE-20731 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Marián Labuda > Fix For: 4.3.1.CR1 > > > Finish button in OpenShift 3 Import OpenShift Application wizard is enabled if the wizard is opened via context menu of a build config even though the repository is already cloned in default git location. This allows users to click on Finish button, but nothing happens. If Import OpenShift Application is opened via context menu of a project or connection or the build config in Import OpenShift Application is selected, then the Finish button for already cloned repositories of a build config is disabled. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21528) Properties view: Show pod status in column for tabbed pod property

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21528?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-21528. --------------------------------- Verified on nightly build of JBT with OpenShift tooling B190. > Properties view: Show pod status in column for tabbed pod property > ------------------------------------------------------------------ > > Key: JBIDE-21528 > URL: https://issues.jboss.org/browse/JBIDE-21528 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Marián Labuda > Assignee: Fred Bricon > Labels: properties > Fix For: 4.3.1.CR1 > > > In new deployment view, more precisely in Properties view and tabbed property Pods, there is a table with pods under a selected project. It would be nice if there would be a column with pod status. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21748) Properties view: Show pod status in column for tabbed pod property

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21748?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-21748: ---------------------------------- Fix Version/s: 4.4.0.Alpha1 (was: 4.3.1.CR1) > Properties view: Show pod status in column for tabbed pod property > ------------------------------------------------------------------ > > Key: JBIDE-21748 > URL: https://issues.jboss.org/browse/JBIDE-21748 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Marián Labuda > Assignee: Fred Bricon > Labels: properties > Fix For: 4.4.0.Alpha1 > > > In new deployment view, more precisely in Properties view and tabbed property Pods, there is a table with pods under a selected project. It would be nice if there would be a column with pod status. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

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 February 2016