February 2016 - jbosstools-issues

[JBoss JIRA] (JBIDE-21624) Add Deploy menu to deployment configs

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21624?page=com.atlassian.jira.plugi... ] Jeff Cantrill commented on JBIDE-21624: --------------------------------------- @fbricon merged rest client changes. > Add Deploy menu to deployment configs > ------------------------------------- > > Key: JBIDE-21624 > URL: https://issues.jboss.org/browse/JBIDE-21624 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Fred Bricon > Assignee: Jeff Cantrill > Priority: Critical > Fix For: 4.3.1.CR1 > > > We currently cannot trigger a deployment of a Deployment Config, like in the webconsole. Hopefully it should be trivial to implement. > * Add context menu in tabs for deploymentconfigs of deployment > * Add context menu to explorer view when selecting deployment (service) > * * There should be only one dc, but choose the one with the latest created timestamp if more than 1 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21628) Server Adapter: Service widget is empty

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21628?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich reassigned JBIDE-21628: --------------------------------------------- Assignee: Viacheslav Kabanovich > Server Adapter: Service widget is empty > --------------------------------------- > > Key: JBIDE-21628 > URL: https://issues.jboss.org/browse/JBIDE-21628 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Viacheslav Kabanovich > Labels: openshift_v3, server_adapter > Attachments: empty_service.png > > > In OpenShift 3 Server Adapter overview are widgets with information related to server adapter. There is a text widget for a service but it is empty although server adapter is connected to a specific service. See following screenshot > !empty_service.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-543) Add missing JBDS TP bits to JBDS IS update site zip

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBTIS-543?page=com.atlassian.jira.plugin.... ] Nick Boldt resolved JBTIS-543. ------------------------------ Resolution: Done > Add missing JBDS TP bits to JBDS IS update site zip > --------------------------------------------------- > > Key: JBTIS-543 > URL: https://issues.jboss.org/browse/JBTIS-543 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 9.0.0.Alpha1 > Environment: Customer Support Portal > Reporter: Mustafa Musaji > Assignee: Nick Boldt > Fix For: 9.0.0.Beta1 > > > Offline ZIP installation allows for JBDSIS tooling to be installed when there is no internet connection available. These zips for the JBDSIS and early access tooling is available from the CSP, however, some dependencies for this tooling is only available on the Target Platform zip. > This TP zip is only available on the jboss.org site https://devstudio.jboss.com/9.0/stable/updates/ and not on the customer portal. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21630) itest timeout not respected

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21630?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-21630: ------------------------------------ I've set "-Dsurefire.itests.timeout=4000 -Dsurefire.timeout=4000" in Jenkins job to see if those values stick. Also added "help:effective-pom" to the test run to see if the values there are different. http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt... >=912 > itest timeout not respected > --------------------------- > > Key: JBIDE-21630 > URL: https://issues.jboss.org/browse/JBIDE-21630 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, server > Affects Versions: 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Mickael Istria > Labels: help_wanted > Fix For: 4.4.0.Alpha1 > > > Server itests are running with a timeout of 2400s, which is the default set in our parent pom [1]. > [1] https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml... > But the server root pom sets a timeout of 3000s [2], which is being ignored [3]: > [2] https://github.com/jbosstools/jbosstools-server/blob/master/pom.xml#L17-L18 > {code} > 13:39:42 [ERROR] Timeout 2400 s exceeded. Process was killed. > {code} > [3] http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt... > So... how can we ensure that the itests get more time to run, so that these extra tests can be run without crashing? Currently, server is showing 2829 tests, but the last time it was blue, we had 3434 tests, so there are about 600 tests for which no results are being logged due to the timeout. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21630) itest timeout not respected

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21630?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-21630: ---------------------------------------- This effective pom looks good... I can't find anything obvious that would suddenly introduce this "2400". Whay you may try is to set also the "surefire.timeout" to 3000 in the pom of as.itests. > itest timeout not respected > --------------------------- > > Key: JBIDE-21630 > URL: https://issues.jboss.org/browse/JBIDE-21630 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, server > Affects Versions: 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Mickael Istria > Labels: help_wanted > Fix For: 4.4.0.Alpha1 > > > Server itests are running with a timeout of 2400s, which is the default set in our parent pom [1]. > [1] https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml... > But the server root pom sets a timeout of 3000s [2], which is being ignored [3]: > [2] https://github.com/jbosstools/jbosstools-server/blob/master/pom.xml#L17-L18 > {code} > 13:39:42 [ERROR] Timeout 2400 s exceeded. Process was killed. > {code} > [3] http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt... > So... how can we ensure that the itests get more time to run, so that these extra tests can be run without crashing? Currently, server is showing 2829 tests, but the last time it was blue, we had 3434 tests, so there are about 600 tests for which no results are being logged due to the timeout. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ERT-78) Improve the information shown while hovering over a variable during a JS debugging session [EBZ#487055]

by Nick Boldt (JIRA)

Nick Boldt created ERT-78: ----------------------------- Summary: Improve the information shown while hovering over a variable during a JS debugging session [EBZ#487055] Key: ERT-78 URL: https://issues.jboss.org/browse/ERT-78 Project: Eclipse Release Train Issue Type: Task Components: JSDT Reporter: Nick Boldt Fix For: Neon (4.6) M6 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ERT-75) Support for Smart Import mechanism [EBZ#464535]

by Nick Boldt (JIRA)

Nick Boldt created ERT-75: ----------------------------- Summary: Support for Smart Import mechanism [EBZ#464535] Key: ERT-75 URL: https://issues.jboss.org/browse/ERT-75 Project: Eclipse Release Train Issue Type: Task Components: m2e Reporter: Nick Boldt Priority: Trivial Fix For: Neon (4.6) M5 A new import framework is currently incubating in e4, with the goal of having it part of Platform UI for Neon. Documentation is available at https://wiki.eclipse.org/E4/UI/Smart_Import . As Maven is one of the cornerstone of Java development, it would be good to have an integration between m2e and this framework available as soon as possible, and to ship it in m2e site or in a m2e incubator site. (but not in main feature nor release train). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ERT-75) Support for Smart Import mechanism [EBZ#464535]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/ERT-75?page=com.atlassian.jira.plugin.sys... ] Nick Boldt resolved ERT-75. --------------------------- Resolution: Done > Support for Smart Import mechanism [EBZ#464535] > ----------------------------------------------- > > Key: ERT-75 > URL: https://issues.jboss.org/browse/ERT-75 > Project: Eclipse Release Train > Issue Type: Task > Components: m2e > Reporter: Nick Boldt > Priority: Trivial > Labels: 1.7.0/Neon_M5, bzira, ui > Fix For: Neon (4.6) M5 > > > A new import framework is currently incubating in e4, with the goal of having it part of Platform UI for Neon. Documentation is available at https://wiki.eclipse.org/E4/UI/Smart_Import . > As Maven is one of the cornerstone of Java development, it would be good to have an integration between m2e and this framework available as soon as possible, and to ship it in m2e site or in a m2e incubator site. (but not in main feature nor release train). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ERT-76) Sync of IJSONModel with editor should be improved/fixed [EBZ#486860]

by Nick Boldt (JIRA)

Nick Boldt created ERT-76: ----------------------------- Summary: Sync of IJSONModel with editor should be improved/fixed [EBZ#486860] Key: ERT-76 URL: https://issues.jboss.org/browse/ERT-76 Project: Eclipse Release Train Issue Type: Task Components: WTP Source Editing Reporter: Nick Boldt IMHO the sync of IJSONModel with editor is the most important and should be done/fixed before fixing, improving other features. But it is the most hard too. At first, we should validate the IJSONModel API The big problem with JSON Editor is that the IJSONModel, IJSONPair, IJSONDocument, etc. There are a lot of copy/paste from XML/CSS plugins so this model and the implementation should be really fixed/improved. For instance completion works when editor is opened, but it is broken after some changes of the text editor. It is because IJSONModel is not very well sync. The most bugs that I see like: * https://bugs.eclipse.org/bugs/show_bug.cgi?id=486606 * https://bugs.eclipse.org/bugs/show_bug.cgi?id=485694 * https://bugs.eclipse.org/bugs/show_bug.cgi?id=486849 * https://bugs.eclipse.org/bugs/show_bug.cgi?id=486524 are linked to this sync problem. So tests https://github.com/angelozerr/eclipse-wtp-json/blob/master/core/org.eclip... must be completed when sync of model is improved. I will try to create a patch for adding tests https://bugs.eclipse.org/bugs/show_bug.cgi?id=486238 It's a very hard task, so good luck to do that. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ERT-77) JSON Editor feature and plugins provide wrong details [EBZ#487050]

by Nick Boldt (JIRA)

Nick Boldt created ERT-77: ----------------------------- Summary: JSON Editor feature and plugins provide wrong details [EBZ#487050] Key: ERT-77 URL: https://issues.jboss.org/browse/ERT-77 Project: Eclipse Release Train Issue Type: Task Components: WTP Source Editing Reporter: Nick Boldt In Eclipse Neon M5, JSON Editor feature and plugins list Angelo Zerr as provider http://screencast.com/t/hxCHZj9NYaXc Also, it seems the feature description is missing -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

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