November 2016 - jbosstools-issues

[JBoss JIRA] (JBIDE-23354) Deploy Docker Wizard: Reset of port mapping whille at least 1 default is present causes NPE

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23354?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-23354. --------------------------------- Verified in DevStudio 10.2.0.AM3 build id AM3-v20161104-1659-B6372. > Deploy Docker Wizard: Reset of port mapping whille at least 1 default is present causes NPE > ------------------------------------------------------------------------------------------- > > Key: JBIDE-23354 > URL: https://issues.jboss.org/browse/JBIDE-23354 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.2.AM2 > Reporter: Marián Labuda > Assignee: Jeff MAURY > Labels: deploy_docker_wizard, openshift_v3 > Fix For: 4.4.2.AM3 > > > In Deploy Image to Docker wizard on the wizard page with routing settings, if I click on Reset while in the table is at least 1 default port mapping (row with non-changed values = default), cause NPE and the default row is shown as empty = name, service port and pod port are shown as blank. > NPE stack trace > {code}Problems occurred when invoking code from plug-in: "org.eclipse.jface". > java.lang.NullPointerException > at org.jboss.tools.openshift.internal.ui.wizard.deployimage.ServicesAndRoutingPage$2.getColumnImage(ServicesAndRoutingPage.java:196) > at org.eclipse.jface.viewers.TableColumnViewerLabelProvider.update(TableColumnViewerLabelProvider.java:67) > at org.eclipse.jface.viewers.ViewerColumn.refresh(ViewerColumn.java:141) > at org.eclipse.jface.viewers.AbstractTableViewer.doUpdateItem(AbstractTableViewer.java:382) > at org.eclipse.jface.viewers.StructuredViewer$UpdateItemSafeRunnable.run(StructuredViewer.java:474) > 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.viewers.StructuredViewer.updateItem(StructuredViewer.java:2170) > at org.eclipse.jface.viewers.AbstractTableViewer.internalRefreshAll(AbstractTableViewer.java:669) > at org.eclipse.jface.viewers.AbstractTableViewer.internalRefresh(AbstractTableViewer.java:607) > at org.eclipse.jface.viewers.AbstractTableViewer.internalRefresh(AbstractTableViewer.java:599) > at org.eclipse.jface.viewers.StructuredViewer.lambda$0(StructuredViewer.java:1519) > at org.eclipse.jface.viewers.StructuredViewer.preservingSelection(StructuredViewer.java:1458) > at org.eclipse.jface.viewers.StructuredViewer.preservingSelection(StructuredViewer.java:1419) > at org.eclipse.jface.viewers.StructuredViewer.refresh(StructuredViewer.java:1519) > at org.eclipse.jface.viewers.ColumnViewer.refresh(ColumnViewer.java:523) > at org.eclipse.jface.viewers.StructuredViewer.refresh(StructuredViewer.java:1478) > at org.jboss.tools.openshift.internal.ui.wizard.deployimage.ServicesAndRoutingPage$7.widgetSelected(ServicesAndRoutingPage.java:402) > 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.jboss.tools.common.ui.WizardUtils.openWizardDialog(WizardUtils.java:257) > at org.jboss.tools.openshift.internal.ui.handler.DeployImageHandler$2$1.run(DeployImageHandler.java:94) > at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) > at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:182) > at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4528) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4146) > 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 (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23372) Resource wizard: lots of empty space to the right of the project settings

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23372?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-23372. --------------------------------- Verified in DevStudio 10.2.0.AM3 build id AM3-v20161104-1659-B6372. > Resource wizard: lots of empty space to the right of the project settings > ------------------------------------------------------------------------- > > Key: JBIDE-23372 > URL: https://issues.jboss.org/browse/JBIDE-23372 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.1.AM2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: application_wizard, resource_wizard, ui > Fix For: 4.4.2.AM3 > > Attachments: empty-horiz-space.png, new-application-wizard-before.png, new-application-wizard.png, new-resource-wizard.png > > > In wizard to create new resources the 1st line that allows one to select the OpenShift project, there's plenty of space to the right. The project combo should be sclaed to use all the available horizontal space so that the widgets are nicely aligned > !empty-horiz-space.png! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23412) Scale To: wrong number of replicas is shown if invoked right after "Deploy latest"

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23412?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-23412. --------------------------------- Closed as a duplicate, original JIRA has been verified. > Scale To: wrong number of replicas is shown if invoked right after "Deploy latest" > ---------------------------------------------------------------------------------- > > Key: JBIDE-23412 > URL: https://issues.jboss.org/browse/JBIDE-23412 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.2.AM2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: deploy_latest, scaling_pods_wizard > Fix For: 4.4.2.AM3 > > Attachments: rc-1-replicas-0.png, rc2-replicas-1.png, replicas-0.png, scale-to-shows-old-rc.ogv > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23030) Scaling a service changes the wrong deployment

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23030?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-23030. --------------------------------- Verified in DevStudio 10.2.0.AM3 build id AM3-v20161104-1659-B6372. > Scaling a service changes the wrong deployment > ---------------------------------------------- > > Key: JBIDE-23030 > URL: https://issues.jboss.org/browse/JBIDE-23030 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM3 > Reporter: Fred Bricon > Assignee: Jeff Cantrill > Priority: Critical > Fix For: 4.4.2.AM3 > > Attachments: rc-1-replicas-0.png, rc2-replicas-1.png, replicas-0.png, scale-to-shows-old-rc.ogv > > > In openshift explorer, when scaling a service that has 2 deployments, it deploys pod from the oldest deployment instead of the latest. Eventually, these pods are killed by openshift. > The workaround is to open the properties view and issue a scale command on a deployment directly. > However, because scaling is such a front-and-center feature from the explorer, I believe it's critical we fix it ASAP > (copied from JBIDE-23412) > The following steps can be seen in the following screencast: > [^scale-to-shows-old-rc.ogv] > # ASSERT: have an app running (ex. nodejs-example) > # ASSERT: In OpenShift Explorer: make sure it has at least 1 pod: pick "Scale To" in the context menu of the service. Dialog shows that there's at least 1 pod currently > # ASSERT: in OpenShift Explorer: there 1 pod shown as child to the service. > # ASSERT: in Properties view, pick "Deployments" tab and see that there's at least 1 deployment (aka replication controller) > # EXEC: in OpenShift explorer: select Service pick "Deploy Latest" > # ASSERT: in Properties view: "Deployments" now shows 2 Deployments > # ASSERT: in OpenShift Explorer you now see 2 children/pods > # EXEC: in OpenShift Explorer: pick "Scale To..." in the context menu of the service > Result: > The current number of pods is shown as 0. > !replicas-0.png! > But it's very sure that this is not true. Behind the scenes a new replication controller was created which deployed a new pod: > !rc2-replicas-1.png! > The old replication controller was turned to have 0 pods. The "Scale To" dialog shows the number of replcas for the old replication controller. > !rc-1-replicas-0.png! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23165) application wizard: IllegalArgumentException in New OpenShift Application Wizard

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23165?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-23165. --------------------------------- Verified in DevStudio 10.2.0.AM3 build id AM3-v20161104-1659-B6372. > application wizard: IllegalArgumentException in New OpenShift Application Wizard > -------------------------------------------------------------------------------- > > Key: JBIDE-23165 > URL: https://issues.jboss.org/browse/JBIDE-23165 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.Final > Environment: Windows 10 Home > OpenJDK 1.8 > Reporter: Denis Golovin > Assignee: Andre Dietisheim > Labels: application_wizard, openshift_v3 > Fix For: 4.4.2.AM2 > > Attachments: error-verifying-user-credentials.png, oc3iare.gif, page-changing-context-menu.ogv, page-changing-new-wizard.ogv, Wrong-direction-screencast.webm > > > {code}java.lang.IllegalArgumentException: > at org.eclipse.core.runtime.Assert.isLegal(Assert.java:63) > at org.eclipse.core.runtime.Assert.isLegal(Assert.java:47) > at org.jboss.tools.openshift.internal.ui.wizard.connection.AdvancedConnectionEditor$ConnectionAdvancedPropertiesProvider.update(AdvancedConnectionEditor.java:191) > at org.jboss.tools.openshift.internal.common.ui.connection.ConnectionWizardPage.onPageWillGetDeactivated(ConnectionWizardPage.java:370) > at org.jboss.tools.openshift.internal.common.ui.wizard.AbstractOpenShiftWizardPage$3.handlePageChanging(AbstractOpenShiftWizardPage.java:121) > at org.eclipse.jface.wizard.WizardDialog$7.run(WizardDialog.java:1540) > 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.wizard.WizardDialog.firePageChanging(WizardDialog.java:1537) > at org.eclipse.jface.wizard.WizardDialog.doPageChanging(WizardDialog.java:890) > at org.eclipse.jface.wizard.WizardDialog.showPage(WizardDialog.java:1177) > at org.eclipse.jface.wizard.WizardDialog.backPressed(WizardDialog.java:404) > at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:415) > 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:4410) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1079) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4228) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3816) > 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.handlers.WizardHandler$New.executeHandler(WizardHandler.java:269) > at org.eclipse.ui.internal.handlers.WizardHandler.execute(WizardHandler.java:290) > 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(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) > at java.lang.reflect.Method.invoke(Unknown Source) > at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:54) > at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:282) > at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:264) > 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:494) > at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:488) > at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:210) > at org.eclipse.ui.internal.handlers.LegacyHandlerService.executeCommand(LegacyHandlerService.java:353) > at org.eclipse.ui.internal.actions.CommandAction.runWithEvent(CommandAction.java:155) > 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:4410) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1079) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4228) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3816) > 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(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) > at java.lang.reflect.Method.invoke(Unknown Source) > 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 (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23440) Hibernate New and Noteworthy for 4.4.2.AM3

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23440?page=com.atlassian.jira.plugi... ] Koen Aers closed JBIDE-23440. ----------------------------- Resolution: Rejected > Hibernate New and Noteworthy for 4.4.2.AM3 > --------------------------------------------------- > > Key: JBIDE-23440 > URL: https://issues.jboss.org/browse/JBIDE-23440 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: hibernate > Reporter: Jeff MAURY > Assignee: Koen Aers > Priority: Critical > > Search for your component's New and Noteworthy issues: > Queries: > * [Completed Hibernate JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [All Completed JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [N&N Task JIRAs for this milestone|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Not...] > * [All N&N Task JIRAs|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Notewor...] > If no N&N issues are found for Hibernate, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for Hibernate by submitting a pull request against: > * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio... > If your PR's commit comment is of the form 'JBIDE-56789 #comment Create N&N for Hibernate4.4.2.AM3 #close', and your github user's email address is the same as your JIRA one, then this JIRA should be closed automatically when the PR is applied. > If there is nothing new or noteworthy for Hibernate for this milestone, please *reject* and *close* this issue. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23413) use Import-Package instead of Require-Bundle for slf4j.api [hibernate]

by Rastislav Wagner (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23413?page=com.atlassian.jira.plugi... ] Rastislav Wagner closed JBIDE-23413. ------------------------------------ verified in github & devstudio rpm > use Import-Package instead of Require-Bundle for slf4j.api [hibernate] > ---------------------------------------------------------------------- > > Key: JBIDE-23413 > URL: https://issues.jboss.org/browse/JBIDE-23413 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate, rpm > Affects Versions: 4.4.2.AM2 > Reporter: Nick Boldt > Assignee: Koen Aers > Priority: Blocker > Fix For: 4.4.2.AM3 > > Attachments: hibernate-working-again-.png, org.hibernate.eclipse.unresolved.req.txt > > > Because hibernate tools use Require-Bundle instead of Import-Package to depend on slf4j.api, this project cannot use the rhel implementation (rh-common-java rpm) version of slf4j.api 1.7.4 .jar when installed via rpm on rhel/fedora. > Here's the line that is causing the problem: > https://github.com/jbosstools/jbosstools-hibernate/blob/master/plugins/or... > We need to switch to using Import-Package to that *any* implementation of this package, regardless of *Bundle-SymbolicName*, can be used. > More info in JBDS-4136 > See also: > http://stackoverflow.com/questions/13959891/why-do-we-need-imported-packa... > http://stackoverflow.com/questions/1865819/when-should-i-use-import-packa... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23415) use Import-Package instead of Require-Bundle for slf4j.api [livereload]

by Rastislav Wagner (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23415?page=com.atlassian.jira.plugi... ] Rastislav Wagner closed JBIDE-23415. ------------------------------------ verified in github & devstudio rpm > use Import-Package instead of Require-Bundle for slf4j.api [livereload] > ----------------------------------------------------------------------- > > Key: JBIDE-23415 > URL: https://issues.jboss.org/browse/JBIDE-23415 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: livereload, rpm > Affects Versions: 4.4.2.AM2 > Reporter: Nick Boldt > Assignee: Xavier Coulon > Priority: Minor > Fix For: 4.4.2.AM3 > > > Because livereload tools use Require-Bundle instead of Import-Package to depend on slf4j.api, this project cannot use the rhel implementation (rh-common-java rpm) version of slf4j.api 1.7.4 .jar when installed via rpm on rhel/fedora. > Here's the line that is causing the problem: > https://github.com/jbosstools/jbosstools-livereload/blob/44af911aba916f0e... > We need to switch to using Import-Package to that *any* implementation of this package, regardless of *Bundle-SymbolicName*, can be used. > More info in JBDS-4136 > See also: > http://stackoverflow.com/questions/13959891/why-do-we-need-imported-packa... > http://stackoverflow.com/questions/1865819/when-should-i-use-import-packa... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4119) Some paths are too long for the uninstaller

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-4119?page=com.atlassian.jira.plugin.... ] Jan Richter updated JBDS-4119: ------------------------------ Fix Version/s: 10.2.0.AM3 (was: 10.2.0.GA) > Some paths are too long for the uninstaller > ------------------------------------------- > > Key: JBDS-4119 > URL: https://issues.jboss.org/browse/JBDS-4119 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 10.2.0.AM2 > Reporter: Jan Richter > Assignee: Jan Richter > Fix For: 10.2.0.AM3 > > > It is possible to install everything and still get 'path too long' error on uninstallation. For example it seems that drive labels are in fact factored into the 255 character path limit in powershell. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4153) Cannot install Fuse Runtime on Windows using the installer

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBDS-4153?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky commented on JBDS-4153: ----------------------------------------- I can also confirm the successful installation on Windows 10 and maxosx 10.11 > Cannot install Fuse Runtime on Windows using the installer > ---------------------------------------------------------- > > Key: JBDS-4153 > URL: https://issues.jboss.org/browse/JBDS-4153 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: installer > Affects Versions: 10.1.0.GA > Reporter: Aurélien Pupier > Assignee: Paul Leacu > Priority: Blocker > Fix For: 10.x > > Attachments: screenshot-1.png, screenshot-2.png, screenshot-3.png > > > On Windows, if using the installer with the Fuse Runtime and keeping it checked, the installation fails. > i used https://devstudio.redhat.com/10.0/staging/updates/integration-stack/10.0.... > !screenshot-1.png|thumbnail! > !screenshot-2.png|thumbnail! > !screenshot-3.png|thumbnail! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

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