January 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-20926) Visual Preview tests fail on windows

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20926?page=com.atlassian.jira.plugi... ] Denis Golovin commented on JBIDE-20926: --------------------------------------- excluded bad slave with additional check &&!dev101-W2k8r2-x86_64 in expression > Visual Preview tests fail on windows > ------------------------------------ > > Key: JBIDE-20926 > URL: https://issues.jboss.org/browse/JBIDE-20926 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: visual-page-editor-core > Affects Versions: 4.4.0.Alpha1 > Environment: Windows IE11 x86_64 > Reporter: Denis Golovin > Assignee: Konstantin Marmalyukov > Fix For: 4.4.0.Alpha1 > > > {code}externalUrlReloadTest(org.jboss.tools.vpe.preview.editor.test.editor.PreviewReloadTest) Time elapsed: 15.671 sec <<< ERROR! > java.lang.Exception: Refresh does not happens > at org.jboss.tools.vpe.preview.editor.test.editor.PreviewReloadTest.externalUrlReloadTest(PreviewReloadTest.java:72) > externalUrlReloadTest(org.jboss.tools.vpe.preview.editor.test.editor.PreviewReloadTest) Time elapsed: 15.681 sec <<< FAILURE! > java.lang.AssertionError: Refresh does not happens > at org.junit.Assert.fail(Assert.java:88) > at org.jboss.tools.vpe.preview.editor.test.editor.VpvTest.failOnException(VpvTest.java:68) > 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:497) > at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50) > at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) > at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47) > at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:33) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) > at org.junit.runners.ParentRunner.run(ParentRunner.java:363) > at org.junit.runners.Suite.runChild(Suite.java:128) > at org.junit.runners.Suite.runChild(Suite.java:27) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) > at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) > at org.junit.runners.ParentRunner.run(ParentRunner.java:363) > at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:264) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153) > at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:124) > 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:497) > at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray2(ReflectionUtils.java:208) > at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:156) > at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:82) > at org.eclipse.tycho.surefire.osgibooter.OsgiSurefireBooter.run(OsgiSurefireBooter.java:91) > at org.eclipse.tycho.surefire.osgibooter.AbstractUITestApplication$1.run(AbstractUITestApplication.java:35) > at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) > at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135) > at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4155) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3772) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1127) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1018) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:157) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:654) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:598) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150) > at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:139) > at org.eclipse.tycho.surefire.osgibooter.UITestApplication.runApplication(UITestApplication.java:31) > at org.eclipse.tycho.surefire.osgibooter.AbstractUITestApplication.run(AbstractUITestApplication.java:120) > at org.eclipse.tycho.surefire.osgibooter.UITestApplication.start(UITestApplication.java:37) > 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:497) > at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:669) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:608) > at org.eclipse.equinox.launcher.Main.run(Main.java:1515) > at org.eclipse.equinox.launcher.Main.main(Main.java:1488){code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (LOCUS-51) Move up to latest Orbit

by Nick Boldt (JIRA)

Nick Boldt created LOCUS-51: ------------------------------- Summary: Move up to latest Orbit Key: LOCUS-51 URL: https://issues.jboss.org/browse/LOCUS-51 Project: JBoss Tools Locus Issue Type: Bug Affects Versions: 1.5.0 Reporter: Nick Boldt Use latest Orbit bundles in Locus target platform. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20689) Skip tests that cannot run on current platform

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20689?page=com.atlassian.jira.plugi... ] Denis Golovin resolved JBIDE-20689. ----------------------------------- Resolution: Done released to master > Skip tests that cannot run on current platform > ---------------------------------------------- > > Key: JBIDE-20689 > URL: https://issues.jboss.org/browse/JBIDE-20689 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: visual-page-editor-core > Affects Versions: 4.4.0.Alpha1 > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 4.4.0.Alpha1 > > > VPE related run without errors only only on certain platforms. They should be skipped during tests execution and appear as skipped in report. As an example javaee tests now fail to pass under Mac OS X. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (LOCUS-49) Add jaxb-xjc, jaxb-core and jaxb-impl to locus

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/LOCUS-49?page=com.atlassian.jira.plugin.s... ] Nick Boldt updated LOCUS-49: ---------------------------- Fix Version/s: 1.6.0 (was: 1.5.0) > Add jaxb-xjc, jaxb-core and jaxb-impl to locus > ---------------------------------------------- > > Key: LOCUS-49 > URL: https://issues.jboss.org/browse/LOCUS-49 > Project: JBoss Tools Locus > Issue Type: Feature Request > Affects Versions: 1.4.0 > Reporter: Paul Leacu > Assignee: Paul Leacu > Fix For: 1.6.0 > > Attachments: locus150.png, locus150updatesite.png, org.jboss.tools.locus.jaxb-core_2.2.7.v20160114-2130.jar, org.jboss.tools.locus.jaxb-xjc_2.2.7.v20160113-1915.jar > > > Request addition of jaxb-xjc and jaxb-impl into Mars/ locus. > This completes the initial request from Fuse Data Transformation and allows the removal of locally captured lib versions of jaxb-xjc and jaxb-impl in favor of JBTIS TP dependencies. > https://repo1.maven.org/maven2/com/sun/xml/bind/jaxb-xjc/2.2.7/jaxb-xjc-2... > https://repo1.maven.org/maven2/com/sun/xml/bind/jaxb-xjc/2.2.7/jaxb-xjc-2... > https://repo1.maven.org/maven2/com/sun/xml/bind/jaxb-impl/2.2.7/jaxb-impl... > https://repo1.maven.org/maven2/com/sun/xml/bind/jaxb-impl/2.2.7/jaxb-impl... > This is needed for Mars/ 9.0.x JBDSIS target platform inclusion. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-545) integration stack docs tells users to install devstudio 9

by Jane Murphey (JIRA)

[ https://issues.jboss.org/browse/JBTIS-545?page=com.atlassian.jira.plugin.... ] Jane Murphey commented on JBTIS-545: ------------------------------------ [~leacu], I think the writer is Nicola Moore. > integration stack docs tells users to install devstudio 9 > --------------------------------------------------------- > > Key: JBTIS-545 > URL: https://issues.jboss.org/browse/JBTIS-545 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Reporter: Max Rydahl Andersen > > I was made aware that docs for Fuse refer users to install devstudio 9 at https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Fuse/6.2.1/ht... > I assume that is a bug since it is Developer Studio 8 that is your target, correct ? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21301) Preferences: path to OC binary is not shown on OpenShift 3 page if binary is on $PATH

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21301?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich commented on JBIDE-21301: ----------------------------------------------- [~mlabuda], can you please try /home/mlabuda/openshift/bin instead of /home/mlabuda/openshift/bin/oc ? The search algorithm considers parts in $PATH as directories, to which command name to be found is appended to test if the file exists. Your $PATH includes the exact command location, not its parent directory. > Preferences: path to OC binary is not shown on OpenShift 3 page if binary is on $PATH > ------------------------------------------------------------------------------------- > > Key: JBIDE-21301 > URL: https://issues.jboss.org/browse/JBIDE-21301 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Marián Labuda > Assignee: Viacheslav Kabanovich > Priority: Minor > Labels: openshift_v3, preferences > Fix For: 4.3.1.Beta2 > > > In JBIDE-21183 was implemented auto-lookup of 'oc' binary on $PATH. This works ok, but in Workbench Preference dialog on OpenShift 3 preference page where location to oc is shown and stored is not this path displayed in this case. If 'oc' binary is located on $PATH it should be also visible on OpenShift 3 preference page. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21066) Extra step in opening terminal in git perspective?

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21066?page=com.atlassian.jira.plugi... ] Len DiMaggio updated JBIDE-21066: --------------------------------- Attachment: Terminal.webm > Extra step in opening terminal in git perspective? > -------------------------------------------------- > > Key: JBIDE-21066 > URL: https://issues.jboss.org/browse/JBIDE-21066 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: upstream > Affects Versions: 4.3.0.Final > Reporter: Len DiMaggio > Assignee: Daniel Azarov > Fix For: 4.3.1.Beta2, 4.4.0.Alpha1 > > Attachments: terminal.png, Terminal.webm > > > If a user opens a terminal view from the git perspective - for example, by performing "show in" for a local repo, an empty terminal view is displayed. The user must then click on the terminal icon to actually open the terminal. This seems like an extra step - why wouldn't we open a terminal when we open the terminal view? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-545) integration stack docs tells users to install devstudio 9

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-545?page=com.atlassian.jira.plugin.... ] Paul Leacu commented on JBTIS-545: ---------------------------------- [~jmurphey] [~fbolton] - can one of you help me with this doc issue? > integration stack docs tells users to install devstudio 9 > --------------------------------------------------------- > > Key: JBTIS-545 > URL: https://issues.jboss.org/browse/JBTIS-545 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Reporter: Max Rydahl Andersen > > I was made aware that docs for Fuse refer users to install devstudio 9 at https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Fuse/6.2.1/ht... > I assume that is a bug since it is Developer Studio 8 that is your target, correct ? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-483) B*MS - Migrate to use new license feature in JBTIS 4.3 / JBDS IS 9

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-483?page=com.atlassian.jira.plugin.... ] Paul Leacu commented on JBTIS-483: ---------------------------------- Unfortunately I can't reference a local nexus repo and I don't have write access to the jbpm releases area. > B*MS - Migrate to use new license feature in JBTIS 4.3 / JBDS IS 9 > ------------------------------------------------------------------ > > Key: JBTIS-483 > URL: https://issues.jboss.org/browse/JBTIS-483 > Project: JBoss Tools Integration Stack > Issue Type: Sub-task > Components: BPEL, BPMN2, drools/ jBPM, jBPM3 > Reporter: Paul Leacu > Assignee: Robert (Bob) Brodt > Fix For: 4.3.0.Beta1 > > Attachments: lic1.png > > > Please make sure that the B*MS IS components are including the new license feature. See parent Jira description for details. > ref: https://github.com/jbosstools/jbosstools-devdoc/blob/master/source/how_to... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21457) Explorer: Show build in explorer deployment view if it any state other then complete

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21457?page=com.atlassian.jira.plugi... ] Jeff Cantrill commented on JBIDE-21457: --------------------------------------- I want to further clarify your expectation: The code explicitly only displays 'app' pods and builds but no 'build' pods. @fbricon do we want to show build pods too? My initial response is no we do not. > Explorer: Show build in explorer deployment view if it any state other then complete > ------------------------------------------------------------------------------------ > > Key: JBIDE-21457 > URL: https://issues.jboss.org/browse/JBIDE-21457 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Labels: openshift_deployment_view > Fix For: 4.3.1.CR1 > > > Display the build in the tree view when it is any non-terminated state ("Complete", "Failed", "Error", "Cancelled"). Expectation is builds should be visible in the tree for a short period of time and then disappear. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 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 January 2016