February 2017 - jbosstools-issues

[JBoss JIRA] (ERT-465) Include plug-in jsdt.integration.tests into org.eclipse.wst.jsdt_tests.feature [EBZ#508353]

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/ERT-465?page=com.atlassian.jira.plugin.sy... ] Ilya Buziuk updated ERT-465: ---------------------------- Story Points: 5 (was: 10) > Include plug-in jsdt.integration.tests into org.eclipse.wst.jsdt_tests.feature [EBZ#508353] > ------------------------------------------------------------------------------------------- > > Key: ERT-465 > URL: https://issues.jboss.org/browse/ERT-465 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Friendly Jira Robot > Assignee: Victor Rubezhny > Labels: General, bzira > > We need to include plug-in jsdt.integration.tests into org.eclipse.wst.jsdt_tests.feature -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ERT-465) Include plug-in jsdt.integration.tests into org.eclipse.wst.jsdt_tests.feature [EBZ#508353]

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/ERT-465?page=com.atlassian.jira.plugin.sy... ] Ilya Buziuk updated ERT-465: ---------------------------- Sprint: devex #128 February 2017 (was: devex #127 February 2017) > Include plug-in jsdt.integration.tests into org.eclipse.wst.jsdt_tests.feature [EBZ#508353] > ------------------------------------------------------------------------------------------- > > Key: ERT-465 > URL: https://issues.jboss.org/browse/ERT-465 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Friendly Jira Robot > Assignee: Victor Rubezhny > Labels: General, bzira > > We need to include plug-in jsdt.integration.tests into org.eclipse.wst.jsdt_tests.feature -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ERT-481) Enhance NodeJS Integration Tests - wait for console to be terminated [EBZ#512025]

by Victor Rubezhny (JIRA)

[ https://issues.jboss.org/browse/ERT-481?page=com.atlassian.jira.plugin.sy... ] Victor Rubezhny updated ERT-481: -------------------------------- Sprint: devex #127 February 2017 > Enhance NodeJS Integration Tests - wait for console to be terminated [EBZ#512025] > --------------------------------------------------------------------------------- > > Key: ERT-481 > URL: https://issues.jboss.org/browse/ERT-481 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Friendly Jira Robot > Labels: General, bzira > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTIS-818) Create a test for FUSETOOLS-1993 (one otherwise)

by Dominik Jelinek (JIRA)

[ https://issues.jboss.org/browse/JBTIS-818?page=com.atlassian.jira.plugin.... ] Dominik Jelinek reassigned JBTIS-818: ------------------------------------- Assignee: Dominik Jelinek (was: Tomáš Sedmík) > Create a test for FUSETOOLS-1993 (one otherwise) > ------------------------------------------------ > > Key: JBTIS-818 > URL: https://issues.jboss.org/browse/JBTIS-818 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: Fuse IDE, QE > Affects Versions: 4.3.1.Final > Reporter: Tomáš Sedmík > Assignee: Dominik Jelinek > Fix For: 4.3.1.Final > > > see https://issues.jboss.org/browse/FUSETOOLS-1993 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23961) Server adapter: "Start/Restart in Debug" is broken for Nodejs

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23961?page=com.atlassian.jira.plugi... ] Pavol Srna commented on JBIDE-23961: ------------------------------------ I've reproduced the issue on (devstudio 10.3.0.GA (should be reverted here)) with following steps: 1) Assert Server Adapter running 2) Restart in Debug 3) Restart in Debug (again). > Server adapter: "Start/Restart in Debug" is broken for Nodejs > ------------------------------------------------------------- > > Key: JBIDE-23961 > URL: https://issues.jboss.org/browse/JBIDE-23961 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.3.Final > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Critical > Labels: debugging, nodejs, server_adapter > Fix For: 4.4.4.AM1 > > Attachments: image-2017-02-16-23-30-21-709.png, server-adapter-erroneous-debugging-state.png > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23890) Application Wizard: Finish is enabled after selecting a builder image, clicking next and then back

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23890?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-23890: ------------------------------- Fix Version/s: 4.4.4.AM1 > Application Wizard: Finish is enabled after selecting a builder image, clicking next and then back > -------------------------------------------------------------------------------------------------- > > Key: JBIDE-23890 > URL: https://issues.jboss.org/browse/JBIDE-23890 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.4.AM1 > Reporter: Jan Richter > Assignee: Jeff MAURY > Labels: application_wizard, openshift_v3 > Fix For: 4.4.4.AM1 > > Attachments: app.png > > > When creating a new application from a builder image, clicking 'next' and then going back again will leave the finish button enabled. > Moreover it will store the image that was selected when next button was clicked so if the user selects a new image and clicks finish, it will still use the original image. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23780) Import Application: uncheck "Use default clone destination" wont recheck if I removed the folder that it''s complaining about

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23780?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-23780: ------------------------------- Fix Version/s: 4.4.4.AM1 (was: 4.5.0.AM1) > Import Application: uncheck "Use default clone destination" wont recheck if I removed the folder that it''s complaining about > ----------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-23780 > URL: https://issues.jboss.org/browse/JBIDE-23780 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.3.AM1 > Reporter: Andre Dietisheim > Assignee: Jeff MAURY > Labels: import_wizard, openshift_v3 > Fix For: 4.4.4.AM1 > > Attachments: clone-destination-already-exists.png, error-even-though-clone-destination-doesnt-exist.png > > > steps to reproduce: > # ASSERT: make sure that you have a folder "jboss-eap-quickstarts" in your default Eclipse git clone destination (if you didnt change your preferences, it will point to ~/git/. If you dont have it yet git clone it from https://github.com/jboss-developer/jboss-eap-quickstarts.git) > # EXEC: create a new application using the "eap64-basic-s2i" template > # ASSERT: the OpenShift resources for your application are created, the import wizard pops up with the following error that complains about the directory already existing: > !clone-destination-already-exists.png! > # EXEC: manually remove the directory (ex. in cmd-line) > # EXEC: uncheck "Use default clone destination:" > Result: > The error wont go away, the wizard is still complaining even though the folder isnt in the way any more. > !error-even-though-clone-destination-doesnt-exist.png! > Hitting "Browse" and pointing to the same folder, that doesnt containt the folder anymore, wont help. The error persists. There' > s no way to work around this, you have to cancel the import and start over again. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23900) Refactor OpenShift server adapter to isolate EAP/Wildfly and NodeJS specific stuff

by Dmitrii Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23900?page=com.atlassian.jira.plugi... ] Dmitrii Bocharov updated JBIDE-23900: ------------------------------------- Sprint: devex #128 February 2017 > Refactor OpenShift server adapter to isolate EAP/Wildfly and NodeJS specific stuff > ---------------------------------------------------------------------------------- > > Key: JBIDE-23900 > URL: https://issues.jboss.org/browse/JBIDE-23900 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.3.Final > Reporter: Jeff MAURY > Assignee: Dmitrii Bocharov > Fix For: 4.4.4.AM1 > > > We should isolate EAP/Wildfly and NodeJS specific stuff for the server adapter into separate classes / extensions > We should also provide a mechanism for the sever adapter to be stack agnostic so that we can add more stacks by just addding an extension > This will be probably required by FUSE integration -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23900) Refactor OpenShift server adapter to isolate EAP/Wildfly and NodeJS specific stuff

by Dmitrii Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23900?page=com.atlassian.jira.plugi... ] Dmitrii Bocharov reassigned JBIDE-23900: ---------------------------------------- Assignee: Dmitrii Bocharov > Refactor OpenShift server adapter to isolate EAP/Wildfly and NodeJS specific stuff > ---------------------------------------------------------------------------------- > > Key: JBIDE-23900 > URL: https://issues.jboss.org/browse/JBIDE-23900 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.3.Final > Reporter: Jeff MAURY > Assignee: Dmitrii Bocharov > Fix For: 4.4.4.AM1 > > > We should isolate EAP/Wildfly and NodeJS specific stuff for the server adapter into separate classes / extensions > We should also provide a mechanism for the sever adapter to be stack agnostic so that we can add more stacks by just addding an extension > This will be probably required by FUSE integration -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23780) Import Application: uncheck "Use default clone destination" wont recheck if I removed the folder that it''s complaining about

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23780?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-23780: ------------------------------- Story Points: 10 Sprint: devex #128 February 2017 > Import Application: uncheck "Use default clone destination" wont recheck if I removed the folder that it''s complaining about > ----------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-23780 > URL: https://issues.jboss.org/browse/JBIDE-23780 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.3.AM1 > Reporter: Andre Dietisheim > Assignee: Jeff MAURY > Labels: import_wizard, openshift_v3 > Fix For: 4.5.0.AM1 > > Attachments: clone-destination-already-exists.png, error-even-though-clone-destination-doesnt-exist.png > > > steps to reproduce: > # ASSERT: make sure that you have a folder "jboss-eap-quickstarts" in your default Eclipse git clone destination (if you didnt change your preferences, it will point to ~/git/. If you dont have it yet git clone it from https://github.com/jboss-developer/jboss-eap-quickstarts.git) > # EXEC: create a new application using the "eap64-basic-s2i" template > # ASSERT: the OpenShift resources for your application are created, the import wizard pops up with the following error that complains about the directory already existing: > !clone-destination-already-exists.png! > # EXEC: manually remove the directory (ex. in cmd-line) > # EXEC: uncheck "Use default clone destination:" > Result: > The error wont go away, the wizard is still complaining even though the folder isnt in the way any more. > !error-even-though-clone-destination-doesnt-exist.png! > Hitting "Browse" and pointing to the same folder, that doesnt containt the folder anymore, wont help. The error persists. There' > s no way to work around this, you have to cancel the import and start over again. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 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 2017