August 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-23046) If call to vagrant service-manager times out, openshift / docker connect should still try to be created

by Rob Stryker (JIRA)

Rob Stryker created JBIDE-23046: ----------------------------------- Summary: If call to vagrant service-manager times out, openshift / docker connect should still try to be created Key: JBIDE-23046 URL: https://issues.jboss.org/browse/JBIDE-23046 Project: Tools (JBoss Tools) Issue Type: Bug Components: cdk, server Affects Versions: 4.4.1.AM3 Reporter: Rob Stryker In Windows, I was experiencing an error where the call to vagrant service-manager was not completing. This wasn't due to the output being unavailable, but rather the process not terminating. The current code throws a TimeoutException, but makes no attempt to check if the output is enough to still create the docker / openshift connections. The code should attempt to survive the error and continue along. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ERT-407) Invoking parameter hint (content assist) causes API error [EBZ#500305]

by Friendly Jira Robot (JIRA)

Friendly Jira Robot created ERT-407: --------------------------------------- Summary: Invoking parameter hint (content assist) causes API error [EBZ#500305] Key: ERT-407 URL: https://issues.jboss.org/browse/ERT-407 Project: Eclipse Release Train Issue Type: Task Components: JSDT Reporter: Friendly Jira Robot Priority: Minor When editing a JavaScript file, invoking parameter hints (via ctrl-shift-space or Edit>Content Assist>Parameter Hints) causes the error The 'org.eclipse.wst.jsdt.ui.IdentifierCompletionProposalComputer' proposal computer from the 'org.eclipse.wst.jsdt.ui' plug-in did not complete normally. The extension violated the API contract of the 'computeContextInformation()' operation. Issue seems to be due to incomplete methods in IdentifierCompletionProposalComputer. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22699) BrowserUtilTest.testCreateBrowser failure

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22699?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-22699: ----------------------------------- Sprint: devex #120 September 2016 (was: devex #119 August 2016) > BrowserUtilTest.testCreateBrowser failure > ----------------------------------------- > > Key: JBIDE-22699 > URL: https://issues.jboss.org/browse/JBIDE-22699 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: common/jst/core > Affects Versions: 4.4.1.AM1 > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Fix For: 4.4.2.AM1 > > > org.jboss.tools.foundation.ui.test.BrowserUtilTest.testCreateBrowser > java.lang.AssertionError: null > at org.junit.Assert.fail(Assert.java:86) > at org.junit.Assert.assertTrue(Assert.java:41) > at org.junit.Assert.assertNotNull(Assert.java:712) > at org.junit.Assert.assertNotNull(Assert.java:722) > at org.jboss.tools.foundation.ui.test.BrowserUtilTest.testCreateBrowser(BrowserUtilTest.java:32) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22699) BrowserUtilTest.testCreateBrowser failure

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22699?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-22699: ----------------------------------- Fix Version/s: 4.4.2.AM1 (was: 4.4.1.Final) > BrowserUtilTest.testCreateBrowser failure > ----------------------------------------- > > Key: JBIDE-22699 > URL: https://issues.jboss.org/browse/JBIDE-22699 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: common/jst/core > Affects Versions: 4.4.1.AM1 > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Fix For: 4.4.2.AM1 > > > org.jboss.tools.foundation.ui.test.BrowserUtilTest.testCreateBrowser > java.lang.AssertionError: null > at org.junit.Assert.fail(Assert.java:86) > at org.junit.Assert.assertTrue(Assert.java:41) > at org.junit.Assert.assertNotNull(Assert.java:712) > at org.junit.Assert.assertNotNull(Assert.java:722) > at org.jboss.tools.foundation.ui.test.BrowserUtilTest.testCreateBrowser(BrowserUtilTest.java:32) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23045) xml validator can't find xsd even though it's specified in xml file

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23045?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-23045: -------------------------------------- Assignee: Rob Stryker cc: [~scabanovich] > xml validator can't find xsd even though it's specified in xml file > ------------------------------------------------------------------- > > Key: JBIDE-23045 > URL: https://issues.jboss.org/browse/JBIDE-23045 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: upstream > Affects Versions: 4.4.0.Final > Reporter: Josef Ludvicek > Assignee: Rob Stryker > Fix For: 4.4.x > > Attachments: examle-blueprint.xml > > > RHDS xml validator can't find xsd schema in following xml file => validation doesn't work > {code:xml} > <?xml version="1.0" encoding="UTF-8"?> >  > <blueprint xmlns="http://www.osgi.org/xmlns/blueprint/v1.0.0" > xmlns:cm="http://aries.apache.org/blueprint/xmlns/blueprint-cm/v1.0.0" > xmlns:enc="http://karaf.apache.org/xmlns/jasypt/v1.0.0" xmlns:jaas="http://karaf.apache.org/xmlns/jaas/v1.0.0"> > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23045) xml validator can't find xsd even though it's specified in xml file

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23045?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-23045: ----------------------------------- Project: Tools (JBoss Tools) (was: Red Hat JBoss Developer Studio (devstudio)) Key: JBIDE-23045 (was: JBDS-4017) Workflow: GIT Pull Request workflow (was: CDW v1) Status: Open (was: New) Docs QE Status: (was: NEW) Affects Version/s: 4.4.0.Final (was: 10.0.0.GA) > xml validator can't find xsd even though it's specified in xml file > ------------------------------------------------------------------- > > Key: JBIDE-23045 > URL: https://issues.jboss.org/browse/JBIDE-23045 > Project: Tools (JBoss Tools) > Issue Type: Bug > Affects Versions: 4.4.0.Final > Reporter: Josef Ludvicek > Attachments: examle-blueprint.xml > > > RHDS xml validator can't find xsd schema in following xml file => validation doesn't work > {code:xml} > <?xml version="1.0" encoding="UTF-8"?> >  > <blueprint xmlns="http://www.osgi.org/xmlns/blueprint/v1.0.0" > xmlns:cm="http://aries.apache.org/blueprint/xmlns/blueprint-cm/v1.0.0" > xmlns:enc="http://karaf.apache.org/xmlns/jasypt/v1.0.0" xmlns:jaas="http://karaf.apache.org/xmlns/jaas/v1.0.0"> > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23045) xml validator can't find xsd even though it's specified in xml file

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23045?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-23045: ----------------------------------- Component/s: upstream > xml validator can't find xsd even though it's specified in xml file > ------------------------------------------------------------------- > > Key: JBIDE-23045 > URL: https://issues.jboss.org/browse/JBIDE-23045 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: upstream > Affects Versions: 4.4.0.Final > Reporter: Josef Ludvicek > Fix For: 4.4.x > > Attachments: examle-blueprint.xml > > > RHDS xml validator can't find xsd schema in following xml file => validation doesn't work > {code:xml} > <?xml version="1.0" encoding="UTF-8"?> >  > <blueprint xmlns="http://www.osgi.org/xmlns/blueprint/v1.0.0" > xmlns:cm="http://aries.apache.org/blueprint/xmlns/blueprint-cm/v1.0.0" > xmlns:enc="http://karaf.apache.org/xmlns/jasypt/v1.0.0" xmlns:jaas="http://karaf.apache.org/xmlns/jaas/v1.0.0"> > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23045) xml validator can't find xsd even though it's specified in xml file

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23045?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-23045: ----------------------------------- Fix Version/s: 4.4.x > xml validator can't find xsd even though it's specified in xml file > ------------------------------------------------------------------- > > Key: JBIDE-23045 > URL: https://issues.jboss.org/browse/JBIDE-23045 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: upstream > Affects Versions: 4.4.0.Final > Reporter: Josef Ludvicek > Fix For: 4.4.x > > Attachments: examle-blueprint.xml > > > RHDS xml validator can't find xsd schema in following xml file => validation doesn't work > {code:xml} > <?xml version="1.0" encoding="UTF-8"?> >  > <blueprint xmlns="http://www.osgi.org/xmlns/blueprint/v1.0.0" > xmlns:cm="http://aries.apache.org/blueprint/xmlns/blueprint-cm/v1.0.0" > xmlns:enc="http://karaf.apache.org/xmlns/jasypt/v1.0.0" xmlns:jaas="http://karaf.apache.org/xmlns/jaas/v1.0.0"> > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23041) Restore Defaults preferences causes exception

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23041?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-23041: -------------------------------------- Assignee: Ilya Buziuk > Restore Defaults preferences causes exception > --------------------------------------------- > > Key: JBIDE-23041 > URL: https://issues.jboss.org/browse/JBIDE-23041 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: visual-page-editor-core > Affects Versions: 4.4.1.AM3 > Reporter: Rastislav Wagner > Assignee: Ilya Buziuk > Fix For: 4.4.1.Final > > > {code} > java.lang.ClassCastException: java.lang.String cannot be cast to java.lang.Boolean > at org.jboss.tools.vpe.preview.editor.VpvEditor$5.propertyChange(VpvEditor.java:328) > at org.eclipse.ui.preferences.ScopedPreferenceStore$3.run(ScopedPreferenceStore.java:350) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.ui.preferences.ScopedPreferenceStore.firePropertyChangeEvent(ScopedPreferenceStore.java:346) > at org.eclipse.ui.preferences.ScopedPreferenceStore.setToDefault(ScopedPreferenceStore.java:543) > at org.eclipse.jface.preference.FieldEditor.store(FieldEditor.java:674) > at org.eclipse.jface.preference.FieldEditorPreferencePage.performOk(FieldEditorPreferencePage.java:344) > at org.jboss.tools.vpe.editor.preferences.VpePreferencesPage.performOk(VpePreferencesPage.java:215) > at org.jboss.tools.common.model.ui.preferences.TabbedPreferencesPage.performOk(TabbedPreferencesPage.java:161) > at org.eclipse.jface.preference.PreferenceDialog$8.run(PreferenceDialog.java:905) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:50) > at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:173) > at org.eclipse.jface.preference.PreferenceDialog.okPressed(PreferenceDialog.java:889) > at org.eclipse.ui.internal.dialogs.FilteredPreferenceDialog.okPressed(FilteredPreferenceDialog.java:409) > at org.eclipse.ui.internal.dialogs.WorkbenchPreferenceDialog.okPressed(WorkbenchPreferenceDialog.java:168) > at org.eclipse.jface.preference.PreferenceDialog.buttonPressed(PreferenceDialog.java:230) > at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:618) > at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:249) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:5219) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1340) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4553) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4143) > at org.eclipse.jface.window.Window.runEventLoop(Window.java:818) > at org.eclipse.jface.window.Window.open(Window.java:794) > at org.eclipse.ui.internal.dialogs.WorkbenchPreferenceDialog.open(WorkbenchPreferenceDialog.java:211) > at org.eclipse.ui.internal.OpenPreferencesAction.run(OpenPreferencesAction.java:63) > at org.eclipse.jface.action.Action.runWithEvent(Action.java:473) > at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:565) > at org.eclipse.jface.action.ActionContributionItem.lambda$4(ActionContributionItem.java:397) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:5219) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1340) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4553) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4143) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1121) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1022) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:150) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:687) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:604) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:148) > at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:138) > at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:388) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:673) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:610) > at org.eclipse.equinox.launcher.Main.run(Main.java:1519) > at org.eclipse.equinox.launcher.Main.main(Main.java:1492) > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22884) test failure in org.jboss.tools.vpe.jsp.test

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22884?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-22884 at 8/25/16 4:44 PM: ------------------------------------------------------------- {code} 16:20:19 [jbosstools-vpe_master] $ bash -xe /tmp/hudson4976757903099325961.sh 16:20:19 + curl 'https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/DevStud...' 16:20:19 % Total % Received % Xferd Average Speed Time Time Time Current 16:20:19 Dload Upload Total Spent Left Speed 16:20:19 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0curl: (7) Failed connect to dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com:443; Connection refused 16:20:19 Build step 'Execute shell' marked build as failure 16:20:19 Taking screenshot.{code} Ah, the joys of RH firewalls between datacentres. :( Curl worked to trigger the job from my own machine, but not from jenkins.mw was (Author: nickboldt): {code} 16:20:19 [jbosstools-vpe_master] $ bash -xe /tmp/hudson4976757903099325961.sh 16:20:19 + curl 'https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/DevStud...' 16:20:19 % Total % Received % Xferd Average Speed Time Time Time Current 16:20:19 Dload Upload Total Spent Left Speed 16:20:19 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0curl: (7) Failed connect to dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com:443; Connection refused 16:20:19 Build step 'Execute shell' marked build as failure 16:20:19 Taking screenshot.{code} Ah, the joys of RH firewalls between datacentres. :( > test failure in org.jboss.tools.vpe.jsp.test > -------------------------------------------- > > Key: JBIDE-22884 > URL: https://issues.jboss.org/browse/JBIDE-22884 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml/html-source-editing, visual-page-editor-core > Affects Versions: 4.4.1.AM3 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Fix For: 4.4.1.Final > > Attachments: 22884.more.fail.txt, _view_.txt, _view_more.txt > > > {code} > 21:32:03 [INFO] org.jboss.tools.vpe.jsp.test ....................... FAILURE [ 01:00 h] > 21:32:04 [ERROR] Failed to execute goal org.eclipse.tycho:tycho-surefire-plugin:0.25.0:test (default-test) on project org.jboss.tools.vpe.jsp.test: An unexpected error occured while launching the test runtime (return code 143). See log for details. -> [Help 1] > {code} -- http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-vpe_master... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 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 August 2016