July 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-20389) Jenkins: inconsistent, regular test failures in openshift/egit

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20389?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-20389: ------------------------------------- Attachment: jenkins-sane.png > Jenkins: inconsistent, regular test failures in openshift/egit > -------------------------------------------------------------- > > Key: JBIDE-20389 > URL: https://issues.jboss.org/browse/JBIDE-20389 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Beta2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Critical > Fix For: 4.3.0.CR1 > > Attachments: jenkins-sane.png, openshift-builds.png > > > Jenkins build for OpenShift has inconsistent (they come and go, different tests affected) test failures. Those cant be reproduced in a local build. > {quote} > Build #33 > http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt... > org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.shouldReturnThatCloneIsAheadOfRemote > org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.shouldReturnThatCloneIsAheadOfRemote > {quote} > {quote} > Build #34: > http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt... > org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.canCommitFileInProject > {quote} > {quote} > Build #35 > http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt... > org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.changedButNotCommittedIsDirty (from org.jboss.tools.openshift.egit.internal.test.EGitTestSuite) > Failing for the past 1 build (Since Unstable#35 ) > java.lang.AssertionError: null > at org.junit.Assert.fail(Assert.java:86) > at org.junit.Assert.assertTrue(Assert.java:41) > at org.junit.Assert.assertTrue(Assert.java:52) > at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.changedButNotCommittedIsDirty(EGitUtilsTest.java:314) > {quote} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20389) Jenkins: inconsistent, regular test failures in openshift/egit

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20389?page=com.atlassian.jira.plugi... ] Andre Dietisheim resolved JBIDE-20389. -------------------------------------- Resolution: Out of Date > Jenkins: inconsistent, regular test failures in openshift/egit > -------------------------------------------------------------- > > Key: JBIDE-20389 > URL: https://issues.jboss.org/browse/JBIDE-20389 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Beta2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Critical > Fix For: 4.3.0.CR1 > > Attachments: jenkins-sane.png, openshift-builds.png > > > Jenkins build for OpenShift has inconsistent (they come and go, different tests affected) test failures. Those cant be reproduced in a local build. > {quote} > Build #33 > http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt... > org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.shouldReturnThatCloneIsAheadOfRemote > org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.shouldReturnThatCloneIsAheadOfRemote > {quote} > {quote} > Build #34: > http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt... > org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.canCommitFileInProject > {quote} > {quote} > Build #35 > http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt... > org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.changedButNotCommittedIsDirty (from org.jboss.tools.openshift.egit.internal.test.EGitTestSuite) > Failing for the past 1 build (Since Unstable#35 ) > java.lang.AssertionError: null > at org.junit.Assert.fail(Assert.java:86) > at org.junit.Assert.assertTrue(Assert.java:41) > at org.junit.Assert.assertTrue(Assert.java:52) > at org.jboss.tools.openshift.egit.internal.test.EGitUtilsTest.changedButNotCommittedIsDirty(EGitUtilsTest.java:314) > {quote} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20376) [origin_intservice_59]Port Forwarding wizard: local random port displayed incorrectly for existing session

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20376?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-20376: ------------------------------------- Summary: [origin_intservice_59]Port Forwarding wizard: local random port displayed incorrectly for existing session (was: [origin_intservice_59]Port Forwarding wizard: local port displayed incorrectly when reopening port forwarding after forwarding with random port) > [origin_intservice_59]Port Forwarding wizard: local random port displayed incorrectly for existing session > ---------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20376 > URL: https://issues.jboss.org/browse/JBIDE-20376 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Beta2, 4.3.0.CR1 > Environment: 3.0.0.Beta2-v20150722-0236-B32 > 3.0.0.CR1-v20150723-1038-B887 > Reporter: Yue Wang > Assignee: Jeff Cantrill > Priority: Critical > Labels: application_wizard, openshift_v3 > Fix For: 4.3.0.CR1 > > > port forwarding with a random port(not 8080) and close the port forwarding window, then open the window again, you will find the 'Local Port' changes to '8080' -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20376) [origin_intservice_59]Port Forwarding wizard: local random port reported incorrectly for existing session

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20376?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-20376: ------------------------------------- Summary: [origin_intservice_59]Port Forwarding wizard: local random port reported incorrectly for existing session (was: [origin_intservice_59]Port Forwarding wizard: local random port displayed incorrectly for existing session) > [origin_intservice_59]Port Forwarding wizard: local random port reported incorrectly for existing session > --------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20376 > URL: https://issues.jboss.org/browse/JBIDE-20376 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Beta2, 4.3.0.CR1 > Environment: 3.0.0.Beta2-v20150722-0236-B32 > 3.0.0.CR1-v20150723-1038-B887 > Reporter: Yue Wang > Assignee: Jeff Cantrill > Priority: Critical > Labels: application_wizard, openshift_v3 > Fix For: 4.3.0.CR1 > > > port forwarding with a random port(not 8080) and close the port forwarding window, then open the window again, you will find the 'Local Port' changes to '8080' -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20401) OpenShift tooling UI should include a link to user docs

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20401?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-20401: ------------------------------------- Could we just have a link to getting started in JBT (living on tools.jboss.org), that itself links to existing OpenShift docs? I prefer having 1 link in the tool than 2 > OpenShift tooling UI should include a link to user docs > ------------------------------------------------------- > > Key: JBIDE-20401 > URL: https://issues.jboss.org/browse/JBIDE-20401 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Reporter: Len DiMaggio > Assignee: Misha Ali > Fix For: 4.3.0.CR1 > > > Given the very different architecture of OpenShift v3 as compared to v2, we should provide users with a link to docs detailing the differences. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20397) [origin_intservice_59]Port forwarding wizard: can "Start All" even though local port is already used (by other process)

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20397?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-20397: ------------------------------------------ I can reproduce this with openshift running via vagrant (Vagrant forwards :8080 to :8080 in the vm - occupies :8080). > [origin_intservice_59]Port forwarding wizard: can "Start All" even though local port is already used (by other process) > ----------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20397 > URL: https://issues.jboss.org/browse/JBIDE-20397 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.CR1 > Environment: 3.0.0.CR1-v20150728-1708-B905 > Reporter: Chunyun Chen > Assignee: Jeff Cantrill > Labels: application_wizard, openshift_v3 > Fix For: 4.3.0.CR1 > > > Port forward successfully even if the relevant local port is used by other process. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20404) [origin_intservice_59]can not open 'Port Forwarding' window after stop forwarding from eclipse console

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20404?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-20404: ------------------------------------------ I can reproduce this. In the Eclipse logs I see the following: {code} org.eclipse.e4.core.di.InjectionException: java.lang.NullPointerException at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:68) at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:252) at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:234) at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132) at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:152) at org.eclipse.core.commands.Command.executeWithChecks(Command.java:493) at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:486) at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:210) at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.executeItem(HandledContributionItem.java:799) at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.handleWidgetSelection(HandledContributionItem.java:675) at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.access$7(HandledContributionItem.java:659) at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem$4.handleEvent(HandledContributionItem.java:592) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4481) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1327) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3819) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3430) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1127) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1018) at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:654) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337) 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.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:380) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235) 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:483) 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) Caused by: java.lang.NullPointerException at org.jboss.tools.openshift.internal.ui.portforwading.PortForwardingWizardModel.<init>(PortForwardingWizardModel.java:56) at org.jboss.tools.openshift.internal.ui.handler.PortForwardingHandler.openDialog(PortForwardingHandler.java:59) at org.jboss.tools.openshift.internal.ui.handler.PortForwardingHandler.execute(PortForwardingHandler.java:53) at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:295) at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:90) 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:483) at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:56) ... 38 more {code} > [origin_intservice_59]can not open 'Port Forwarding' window after stop forwarding from eclipse console > ------------------------------------------------------------------------------------------------------ > > Key: JBIDE-20404 > URL: https://issues.jboss.org/browse/JBIDE-20404 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.CR1 > Environment: 3.0.0.CR1-v20150729-1035-B906 > Reporter: Yue Wang > Assignee: Jeff Cantrill > Priority: Critical > Labels: application_wizard, openshift_v3 > Fix For: 4.3.0.CR1 > > > 'Port Forwarding' window doesn't pop up after stop forwarding from eclipse console. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20401) OpenShift tooling UI should include a link to user docs

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20401?page=com.atlassian.jira.plugi... ] Len DiMaggio commented on JBIDE-20401: -------------------------------------- +1 for Marian's suggestion - we should both provide a link to the existing OpenShift docs AND provide a (new) short v3 getting started guide. This new guide can highlight the user stories that we support with the v3 tooling and JBDS 9 - thx! > OpenShift tooling UI should include a link to user docs > ------------------------------------------------------- > > Key: JBIDE-20401 > URL: https://issues.jboss.org/browse/JBIDE-20401 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Reporter: Len DiMaggio > Assignee: Misha Ali > Fix For: 4.3.0.CR1 > > > Given the very different architecture of OpenShift v3 as compared to v2, we should provide users with a link to docs detailing the differences. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3454) Mobile Hybrid Project not opening on the emulator

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBDS-3454?page=com.atlassian.jira.plugin.... ] Gorkem Ercan commented on JBDS-3454: ------------------------------------ You are probably missing "SDK platform" see https://developer.android.com/sdk/installing/adding-packages.html > Mobile Hybrid Project not opening on the emulator > ------------------------------------------------- > > Key: JBDS-3454 > URL: https://issues.jboss.org/browse/JBDS-3454 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: aerogear-hybrid > Affects Versions: 9.0.0.Alpha2 > Reporter: Supriya Bharadwaj > Assignee: Gorkem Ercan > Priority: Minor > Attachments: create_new_avd.png, error_project29july.log > > > I am trying to create a Mobile Hybrid project using the Mobile Hybrid Project wizard in JBoss Central. After its creation, the project does not open on the emulator. Also, if I export the project and try installing the apk file on a mobile android platform I get an "Application not installed" message. On certain environments (JBDS 9.0.0Alpha2 on RHEL 7) while trying to export the project it throws a "not an android project" error. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3276) JBDS-IS Installer

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBDS-3276?page=com.atlassian.jira.plugin.... ] Len DiMaggio commented on JBDS-3276: ------------------------------------ What is the current thinking on this question? Are we proposing one of these options? * A single installer, that would include JBDS and JBDS-IS, or * 2 installers - one for (JBDS), and a second for (JBDS + JBDSIS) > JBDS-IS Installer > ----------------- > > Key: JBDS-3276 > URL: https://issues.jboss.org/browse/JBDS-3276 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: installer, integration-platform, requirements > Affects Versions: 8.0.0.GA > Reporter: Burr Sutter > Assignee: Paul Leacu > Attachments: Red Hat JBoss Developer Studio 9.0.0.Alpha2_105.png > > > As a Fuse, integration-focused developer, I need a downloadable installer that will allow me to quickly and easily install JBDS with Fuse capabilities. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 8 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 July 2015