February 2016 - jbosstools-issues

[JBoss JIRA] (JBDS-3575) Add Fedora 22 and 23 to the support matrix

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-3575?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-3575: ----------------------------- > Add Fedora 22 and 23 to the support matrix > ------------------------------------------ > > Key: JBDS-3575 > URL: https://issues.jboss.org/browse/JBDS-3575 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: requirements > Affects Versions: 9.1.0.Beta1 > Reporter: Martin Malina > Assignee: Martin Malina > Fix For: 9.1.0.GA > > > We should update the support matrix of JBDS to include the latest Fedora releases: 22 and 23. At the same time, 21 can be dropped. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3575) Add Fedora 22 and 23 to the support matrix

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-3575?page=com.atlassian.jira.plugin.... ] CDW Engine reassigned JBDS-3575: -------------------------------- > Add Fedora 22 and 23 to the support matrix > ------------------------------------------ > > Key: JBDS-3575 > URL: https://issues.jboss.org/browse/JBDS-3575 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: requirements > Affects Versions: 9.1.0.Beta1 > Reporter: Martin Malina > Assignee: Martin Malina > Fix For: 9.1.0.GA > > > We should update the support matrix of JBDS to include the latest Fedora releases: 22 and 23. At the same time, 21 can be dropped. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3575) Add Fedora 22 and 23 to the support matrix

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3575?page=com.atlassian.jira.plugin.... ] Alexey Kazakov updated JBDS-3575: --------------------------------- > Add Fedora 22 and 23 to the support matrix > ------------------------------------------ > > Key: JBDS-3575 > URL: https://issues.jboss.org/browse/JBDS-3575 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: requirements > Affects Versions: 9.1.0.Beta1 > Reporter: Martin Malina > Assignee: Martin Malina > Fix For: 9.1.0.GA > > > We should update the support matrix of JBDS to include the latest Fedora releases: 22 and 23. At the same time, 21 can be dropped. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-20915) HTML Page is not refreshed after page is changed in web browser with enabled LiveReload

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20915?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-20915: ----------------------------------- Fix Version/s: (was: 4.3.1.CR1) > HTML Page is not refreshed after page is changed in web browser with enabled LiveReload > --------------------------------------------------------------------------------------- > > Key: JBIDE-20915 > URL: https://issues.jboss.org/browse/JBIDE-20915 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: livereload > Affects Versions: 4.3.0.CR2 > Environment: JBDS 9.0.0.GA-v20150925-1252-B116 > Reporter: Vlado Pakan > Assignee: Xavier Coulon > Fix For: 4.4.0.Alpha1 > > > 1. Import HTML 5 project from JBoss Central > 2. Run it on server > 3. Open Server view, expand running server, select HTML 5 project, click on context menu 'Show In' > 'Web Browser via LiveReolad Server' > ASSERT: index.html page is opened in system web browser > 4. Make some changes to opened page and save them. > ASSERT: Page is redisplayed in web browser and changes made to page are visible in web browser. > Repeat step 4. couple of times > ERROR: Page in web browser blinked seems to be redisplayed but content of page displayed in web browser is not changed -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21772) Watch client errors with unknown enum type: ChangeType.ERROR

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-21772: ---------------------------------------- Summary: Watch client errors with unknown enum type: ChangeType.ERROR Key: JBIDE-21772 URL: https://issues.jboss.org/browse/JBIDE-21772 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.3.1.CR1 Reporter: Andre Dietisheim I dont have a consistent pattern for this so far: In JBoss Tools (openShift) it happened when I created a new application from eap-basic-http-s2i template and tried to create a server adapter for it. It didnt happen in my 1st attempt, it only happend on the 2nd and not on any further attempt. Those other attemps errored with a 404 when the wizard tried to get the image stream tags. The exact stacktrace (which was repeated n-times in the Eclipse logs) is: {code} 2016-02-24 17:05:14.767:WARN:coir.WatchClient$WatchEndpoint:WebSocketClient@1099857077-11028: Unhandled Error (closing connection) java.lang.IllegalArgumentException: No enum constant com.openshift.restclient.IOpenShiftWatchListener.ChangeType.ERROR at java.lang.Enum.valueOf(Enum.java:238) at com.openshift.restclient.IOpenShiftWatchListener$ChangeType.valueOf(IOpenShiftWatchListener.java:45) at com.openshift.internal.restclient.WatchClient$WatchEndpoint.onWebSocketText(WatchClient.java:102) at org.eclipse.jetty.websocket.common.events.JettyListenerEventDriver.onTextMessage(JettyListenerEventDriver.java:128) at org.eclipse.jetty.websocket.common.message.SimpleTextMessage.messageComplete(SimpleTextMessage.java:69) at org.eclipse.jetty.websocket.common.events.AbstractEventDriver.appendMessage(AbstractEventDriver.java:64) at org.eclipse.jetty.websocket.common.events.JettyListenerEventDriver.onTextFrame(JettyListenerEventDriver.java:122) at org.eclipse.jetty.websocket.common.events.AbstractEventDriver.incomingFrame(AbstractEventDriver.java:160) at org.eclipse.jetty.websocket.common.WebSocketSession.incomingFrame(WebSocketSession.java:309) at org.eclipse.jetty.websocket.common.extensions.ExtensionStack.incomingFrame(ExtensionStack.java:214) at org.eclipse.jetty.websocket.common.Parser.notifyFrame(Parser.java:220) at org.eclipse.jetty.websocket.common.Parser.parse(Parser.java:258) at org.eclipse.jetty.websocket.common.io.AbstractWebSocketConnection.readParse(AbstractWebSocketConnection.java:628) at org.eclipse.jetty.websocket.common.io.AbstractWebSocketConnection.onFillable(AbstractWebSocketConnection.java:476) at org.eclipse.jetty.io.AbstractConnection$2.run(AbstractConnection.java:540) at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:635) at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:555) at java.lang.Thread.run(Thread.java:745) {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21753) Explorer: connection name overlaps its icon until expanded with GTK3

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21753?page=com.atlassian.jira.plugi... ] Snjezana Peco commented on JBIDE-21753: --------------------------------------- I can't reproduce the issue on Neon, Mars.1 and openshift master. I have tested GTK 3.14.13, GTK 3.16.7 and GTK 3.18.7. It is possible that you have faced the issue described in https://bugs.eclipse.org/bugs/show_bug.cgi?id=469277 that was fixed in Neon M3. [~jrichter1], What version of Eclipse/JBT are you using? Can you reproduce the issue on Neon? > Explorer: connection name overlaps its icon until expanded with GTK3 > -------------------------------------------------------------------- > > Key: JBIDE-21753 > URL: https://issues.jboss.org/browse/JBIDE-21753 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift, upstream > Affects Versions: 4.3.1.CR1 > Reporter: Jan Richter > Assignee: Snjezana Peco > Priority: Minor > Labels: gtk3 > Fix For: 4.4.0.Alpha1 > > Attachments: connection.png, explorer-view-connections.png > > > This is what the explorer looks like when I start up the tooling with GTK3: > !connection.png|thumbnail! > Expanding the connection will shift the text to its proper position. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21732) Server Adapter: Improve routing selection group in New OpenShift Server adapter wizard

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21732?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich commented on JBIDE-21732: ----------------------------------------------- Following XChat discussion, pull request is updated according to screenshots with "Advanced >>" button. > Server Adapter: Improve routing selection group in New OpenShift Server adapter wizard > -------------------------------------------------------------------------------------- > > Key: JBIDE-21732 > URL: https://issues.jboss.org/browse/JBIDE-21732 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Labels: openshift_v3, server_adapter > Attachments: default_route_os3.gliffy, EnhancedRouteGroup.png, NewServer_Advanced.png, NewServer_Advanced_Expanded.png, use-default-git-clone-destination.png > > > Currently there is a group called "Default Route" and there is a selection of a routing and checkbox for it. See attached diagram for proposed layout. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21694) eap quickstart jaxws-retail fails to compile

by Rafael Benevides (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21694?page=com.atlassian.jira.plugi... ] Rafael Benevides resolved JBIDE-21694. -------------------------------------- Resolution: Done EAP 7.x Quickstarts was ok and WildFly 10.x quickstarts have been fixed with this commit: https://github.com/wildfly/quickstart/commit/c26b8a0099303ebccf5e3b5dcbe8... > eap quickstart jaxws-retail fails to compile > -------------------------------------------- > > Key: JBIDE-21694 > URL: https://issues.jboss.org/browse/JBIDE-21694 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven, upstream > Affects Versions: 4.3.1.Beta2 > Reporter: Rob Stryker > Assignee: Rafael Benevides > Fix For: 4.3.1.CR1 > > > 1) git clone git@github.com:jboss-developer/jboss-eap-quickstarts.git > 2) git checkout 7.0.x-develop > 3) import jaxws-retail folder as maven project > 4) witness compilation errors > The same can be replicated in http://github.com/wildfly/quickstart in the same jaxws-retail folder. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21732) Server Adapter: Improve routing selection group in New OpenShift Server adapter wizard

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21732?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich updated JBIDE-21732: ------------------------------------------ Attachment: NewServer_Advanced_Expanded.png > Server Adapter: Improve routing selection group in New OpenShift Server adapter wizard > -------------------------------------------------------------------------------------- > > Key: JBIDE-21732 > URL: https://issues.jboss.org/browse/JBIDE-21732 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Labels: openshift_v3, server_adapter > Attachments: default_route_os3.gliffy, EnhancedRouteGroup.png, NewServer_Advanced.png, NewServer_Advanced_Expanded.png, use-default-git-clone-destination.png > > > Currently there is a group called "Default Route" and there is a selection of a routing and checkbox for it. See attached diagram for proposed layout. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21760) NPE is thrown on addition of a first pod-service mapping in Deploy docker image wizard

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21760?page=com.atlassian.jira.plugi... ] Fred Bricon reassigned JBIDE-21760: ----------------------------------- Assignee: Viacheslav Kabanovich > NPE is thrown on addition of a first pod-service mapping in Deploy docker image wizard > -------------------------------------------------------------------------------------- > > Key: JBIDE-21760 > URL: https://issues.jboss.org/browse/JBIDE-21760 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Viacheslav Kabanovich > Labels: docker, openshift_v3 > Fix For: 4.3.1.CR1 > > Attachments: npe_docker.png > > > In Deploy Docker Image wizard on 3rd wizard page, where service and pod port mapping is located, NPE is thrown when adding a new mapping and it is first (table displaying mapped service-pod is empty). > !npe_docker.png! > Stacktrace from error log: > {code} > java.lang.NullPointerException > at org.jboss.tools.openshift.internal.ui.wizard.deployimage.ServicePortDialog$PodPortValidator.validate(ServicePortDialog.java:154) > at org.eclipse.core.databinding.UpdateValueStrategy.validateAfterConvert(UpdateValueStrategy.java:442) > at org.eclipse.core.databinding.ValueBinding$3.run(ValueBinding.java:179) > at org.eclipse.core.databinding.observable.Realm$1.run(Realm.java:150) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.core.databinding.observable.Realm.safeRun(Realm.java:154) > at org.eclipse.core.databinding.observable.Realm.exec(Realm.java:172) > at org.eclipse.core.databinding.ValueBinding.doUpdate(ValueBinding.java:158) > at org.eclipse.core.databinding.ValueBinding.access$4(ValueBinding.java:147) > at org.eclipse.core.databinding.ValueBinding$1.handleValueChange(ValueBinding.java:46) > at org.eclipse.core.databinding.observable.value.ValueChangeEvent.dispatch(ValueChangeEvent.java:63) > at org.eclipse.core.databinding.observable.ChangeManager.fireEvent(ChangeManager.java:119) > at org.eclipse.core.databinding.observable.value.DecoratingObservableValue.fireValueChange(DecoratingObservableValue.java:57) > at org.eclipse.core.databinding.observable.value.DecoratingObservableValue.handleValueChange(DecoratingObservableValue.java:99) > at org.eclipse.core.databinding.observable.value.DecoratingObservableValue$1.handleValueChange(DecoratingObservableValue.java:72) > at org.eclipse.core.databinding.observable.value.ValueChangeEvent.dispatch(ValueChangeEvent.java:63) > at org.eclipse.core.databinding.observable.ChangeManager.fireEvent(ChangeManager.java:119) > at org.eclipse.core.databinding.observable.value.AbstractObservableValue.fireValueChange(AbstractObservableValue.java:74) > at org.eclipse.core.internal.databinding.property.value.SimplePropertyObservableValue.notifyIfChanged(SimplePropertyObservableValue.java:127) > at org.eclipse.core.internal.databinding.property.value.SimplePropertyObservableValue.access$2(SimplePropertyObservableValue.java:119) > at org.eclipse.core.internal.databinding.property.value.SimplePropertyObservableValue$1$1.run(SimplePropertyObservableValue.java:69) > at org.eclipse.core.databinding.observable.Realm$1.run(Realm.java:150) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.core.databinding.observable.Realm.safeRun(Realm.java:154) > at org.eclipse.core.databinding.observable.Realm.exec(Realm.java:172) > at org.eclipse.core.internal.databinding.property.value.SimplePropertyObservableValue$1.handleEvent(SimplePropertyObservableValue.java:65) > at org.eclipse.core.databinding.property.NativePropertyListener.fireChange(NativePropertyListener.java:65) > at org.eclipse.jface.internal.databinding.swt.WidgetListener.handleEvent(WidgetListener.java:56) > 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:1329) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3819) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3430) > at org.eclipse.jface.window.Window.runEventLoop(Window.java:827) > at org.eclipse.jface.window.Window.open(Window.java:803) > at org.jboss.tools.openshift.internal.ui.wizard.deployimage.ServicePortDialog.open(ServicePortDialog.java:188) > at org.jboss.tools.openshift.internal.ui.wizard.deployimage.ServicesAndRoutingPage$1.widgetSelected(ServicesAndRoutingPage.java:191) > at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248) > 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:1329) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3819) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3430) > at org.eclipse.jface.window.Window.runEventLoop(Window.java:827) > at org.eclipse.jface.window.Window.open(Window.java:803) > at org.jboss.tools.common.ui.WizardUtils.openWizardDialog(WizardUtils.java:257) > at org.jboss.tools.openshift.internal.ui.handler.DeployImageHandler.execute(DeployImageHandler.java:58) > 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:497) > at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:56) > 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:1329) > 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: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, 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 2016