[JBoss JIRA] (JBIDE-18740) Broken Mobile Engine download - JsonIOException
by Pavol Srna (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18740?page=com.atlassian.jira.plugi... ]
Pavol Srna updated JBIDE-18740:
-------------------------------
Environment: Ubuntu 12.04, Ubuntu 14.04 - with encrypted filesystem (was: Ubuntu 12.04, Ubuntu 14.04)
Workaround Description: don't run the tooling on encrypted partition / (file system)
Workaround: Workaround Exists
> Broken Mobile Engine download - JsonIOException
> -----------------------------------------------
>
> Key: JBIDE-18740
> URL: https://issues.jboss.org/browse/JBIDE-18740
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid
> Affects Versions: 4.2.0.Final
> Environment: Ubuntu 12.04, Ubuntu 14.04 - with encrypted filesystem
> Reporter: Pavol Srna
> Assignee: Gorkem Ercan
> Priority: Critical
> Fix For: 4.2.1.Final
>
> Attachments: cordova.png, cordova_local.png, eclipse.log, local_search.log
>
>
> {code}
> com.google.gson.JsonIOException: java.io.IOException: Attempted read from closed stream.
> at com.google.gson.internal.Streams.parse(Streams.java:57)
> at com.google.gson.JsonParser.parse(JsonParser.java:84)
> at org.eclipse.thym.core.engine.internal.cordova.DefaultEngineRepoProvider.getEngines(DefaultEngineRepoProvider.java:111)
> at org.eclipse.thym.core.engine.internal.cordova.CordovaEngineProvider.getDownloadableVersions(CordovaEngineProvider.java:143)
> at org.eclipse.thym.ui.internal.engine.EngineDownloadDialog.createDialogArea(EngineDownloadDialog.java:245)
> at org.eclipse.jface.dialogs.TitleAreaDialog.createContents(TitleAreaDialog.java:161)
> at org.eclipse.thym.ui.internal.engine.EngineDownloadDialog.createContents(EngineDownloadDialog.java:183)
> at org.eclipse.jface.window.Window.create(Window.java:435)
> at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1101)
> at org.eclipse.jface.window.Window.open(Window.java:797)
> at org.eclipse.thym.ui.internal.engine.AvailableCordovaEnginesSection$5.handleEvent(AvailableCordovaEnginesSection.java:338)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4454)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1388)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3799)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3409)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:832)
> at org.eclipse.jface.window.Window.open(Window.java:808)
> 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:294)
> 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:55)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:247)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:229)
> at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132)
> at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:149)
> at org.eclipse.core.commands.Command.executeWithChecks(Command.java:499)
> at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508)
> at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:210)
> at org.eclipse.ui.internal.handlers.LegacyHandlerService.executeCommand(LegacyHandlerService.java:343)
> at org.eclipse.ui.internal.actions.CommandAction.runWithEvent(CommandAction.java:159)
> at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:595)
> at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:511)
> at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:420)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4454)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1388)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3799)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3409)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1151)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1032)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:148)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:636)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:579)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:135)
> 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:648)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1465)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1438)
> Caused by: java.io.IOException: Attempted read from closed stream.
> at org.apache.http.impl.io.ContentLengthInputStream.read(ContentLengthInputStream.java:172)
> at org.apache.http.conn.EofSensorInputStream.read(EofSensorInputStream.java:138)
> at sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:284)
> at sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:326)
> at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:178)
> at java.io.InputStreamReader.read(InputStreamReader.java:184)
> at com.google.gson.stream.JsonReader.fillBuffer(JsonReader.java:825)
> at com.google.gson.stream.JsonReader.nextNonWhitespace(JsonReader.java:878)
> at com.google.gson.stream.JsonReader.consumeNonExecutePrefix(JsonReader.java:405)
> at com.google.gson.stream.JsonReader.peek(JsonReader.java:364)
> at com.google.gson.internal.Streams.parse(Streams.java:42)
> ... 65 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 8 months
[JBoss JIRA] (JBIDE-18740) Broken Mobile Engine download - JsonIOException
by Pavol Srna (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18740?page=com.atlassian.jira.plugi... ]
Pavol Srna commented on JBIDE-18740:
------------------------------------
Hi [~gercan],
I think that the bug shows up when the filesystem is encrypted. Can you try that please?
I have 2 hdd partitions - one is encrypted and the other is not. I can run successfully when it lives on the unencrypted partition and I hit the issue when using the encrypted one.
Can you please look into that?
Thanks.
> Broken Mobile Engine download - JsonIOException
> -----------------------------------------------
>
> Key: JBIDE-18740
> URL: https://issues.jboss.org/browse/JBIDE-18740
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid
> Affects Versions: 4.2.0.Final
> Environment: Ubuntu 12.04, Ubuntu 14.04
> Reporter: Pavol Srna
> Assignee: Gorkem Ercan
> Priority: Critical
> Fix For: 4.2.1.Final
>
> Attachments: cordova.png, cordova_local.png, eclipse.log, local_search.log
>
>
> {code}
> com.google.gson.JsonIOException: java.io.IOException: Attempted read from closed stream.
> at com.google.gson.internal.Streams.parse(Streams.java:57)
> at com.google.gson.JsonParser.parse(JsonParser.java:84)
> at org.eclipse.thym.core.engine.internal.cordova.DefaultEngineRepoProvider.getEngines(DefaultEngineRepoProvider.java:111)
> at org.eclipse.thym.core.engine.internal.cordova.CordovaEngineProvider.getDownloadableVersions(CordovaEngineProvider.java:143)
> at org.eclipse.thym.ui.internal.engine.EngineDownloadDialog.createDialogArea(EngineDownloadDialog.java:245)
> at org.eclipse.jface.dialogs.TitleAreaDialog.createContents(TitleAreaDialog.java:161)
> at org.eclipse.thym.ui.internal.engine.EngineDownloadDialog.createContents(EngineDownloadDialog.java:183)
> at org.eclipse.jface.window.Window.create(Window.java:435)
> at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1101)
> at org.eclipse.jface.window.Window.open(Window.java:797)
> at org.eclipse.thym.ui.internal.engine.AvailableCordovaEnginesSection$5.handleEvent(AvailableCordovaEnginesSection.java:338)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4454)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1388)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3799)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3409)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:832)
> at org.eclipse.jface.window.Window.open(Window.java:808)
> 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:294)
> 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:55)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:247)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:229)
> at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132)
> at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:149)
> at org.eclipse.core.commands.Command.executeWithChecks(Command.java:499)
> at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508)
> at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:210)
> at org.eclipse.ui.internal.handlers.LegacyHandlerService.executeCommand(LegacyHandlerService.java:343)
> at org.eclipse.ui.internal.actions.CommandAction.runWithEvent(CommandAction.java:159)
> at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:595)
> at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:511)
> at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:420)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4454)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1388)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3799)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3409)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1151)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1032)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:148)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:636)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:579)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:135)
> 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:648)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1465)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1438)
> Caused by: java.io.IOException: Attempted read from closed stream.
> at org.apache.http.impl.io.ContentLengthInputStream.read(ContentLengthInputStream.java:172)
> at org.apache.http.conn.EofSensorInputStream.read(EofSensorInputStream.java:138)
> at sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:284)
> at sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:326)
> at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:178)
> at java.io.InputStreamReader.read(InputStreamReader.java:184)
> at com.google.gson.stream.JsonReader.fillBuffer(JsonReader.java:825)
> at com.google.gson.stream.JsonReader.nextNonWhitespace(JsonReader.java:878)
> at com.google.gson.stream.JsonReader.consumeNonExecutePrefix(JsonReader.java:405)
> at com.google.gson.stream.JsonReader.peek(JsonReader.java:364)
> at com.google.gson.internal.Streams.parse(Streams.java:42)
> ... 65 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 8 months
[JBoss JIRA] (JBIDE-18820) define how to handle ide.properties and avoid parent pom to always change
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18820?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-18820:
----------------------------------------
A) they use the APIs, not directly the values in ide-config.properties. APIs would remain in Foundation, not the configuration itself. The configuration is only necessary at test/run time. For tests, we could use a Mock. For runtime, then it would mean that anyone installing a component which requires properties would need to also install a propertyProvider (aka branding plugin), that might be an optional dependency on the feature.
We could also think about leveraging more abstract dependency definition, as permitted by OSGi, and use Provide/Require-Capability. The Foundation bundles would require the necessary capability, and mock, JBoss Tools and JBDS providers here would provide it, so p2 would get one according to what's available.
> define how to handle ide.properties and avoid parent pom to always change
> -------------------------------------------------------------------------
>
> Key: JBIDE-18820
> URL: https://issues.jboss.org/browse/JBIDE-18820
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: build
> Reporter: Max Rydahl Andersen
>
> As illustrated in JBIDE-18806 our current setup of how ide.properties and project versioning are not working or at least we seem to not get it updated right.
> Current workaround applied is that parent pom now again defines the global version even though this is not reliable at all since not all plugins will be rebuilt. (see JBIDE-13452 for earlier attempts on this)
> Opening this jira to make sure we walkthrough and write down which values should be in ide.properties and what level (4.2.0.CR1, 4.2.0 or 4.2. etc), when they get updated (hopefully rarely) and how to avoid parent pom from always having to respin because of a maintanence release.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 8 months
[JBoss JIRA] (JBIDE-18820) define how to handle ide.properties and avoid parent pom to always change
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18820?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-18820:
---------------------------------------------
A) *any* plugin need to be able to use it. which is why we put it in foundation not central.
B) yes so please show me how you *dont* include it and still solves A.
> define how to handle ide.properties and avoid parent pom to always change
> -------------------------------------------------------------------------
>
> Key: JBIDE-18820
> URL: https://issues.jboss.org/browse/JBIDE-18820
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: build
> Reporter: Max Rydahl Andersen
>
> As illustrated in JBIDE-18806 our current setup of how ide.properties and project versioning are not working or at least we seem to not get it updated right.
> Current workaround applied is that parent pom now again defines the global version even though this is not reliable at all since not all plugins will be rebuilt. (see JBIDE-13452 for earlier attempts on this)
> Opening this jira to make sure we walkthrough and write down which values should be in ide.properties and what level (4.2.0.CR1, 4.2.0 or 4.2. etc), when they get updated (hopefully rarely) and how to avoid parent pom from always having to respin because of a maintanence release.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 8 months
[JBoss JIRA] (JBIDE-17844) Server –> Show in JMX Navigator does not show the server, just opens the view
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17844?page=com.atlassian.jira.plugi... ]
Martin Malina updated JBIDE-17844:
----------------------------------
Fix Version/s: 4.2.1.CR1
(was: 4.2.1.Final)
> Server –> Show in JMX Navigator does not show the server, just opens the view
> -----------------------------------------------------------------------------
>
> Key: JBIDE-17844
> URL: https://issues.jboss.org/browse/JBIDE-17844
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jmx, server
> Affects Versions: 4.2.0.Beta3
> Environment: JBDS 8.0.0.Beta3 B172
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.2.1.CR1
>
>
> When you start a server and then right-click it in the server view and select Show in JMX Navigator, the JMX Navigator view will be opened for you and you will be taken there, but you will only be shown the 3 top level elements.
> You should really be taken straight to the given server in that view. And possibly even connect to it - right now it stays disconnected.
> Interesting is that when you do it again, you will be taken to the server correctly.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 8 months
[JBoss JIRA] (JBIDE-17844) Server –> Show in JMX Navigator does not show the server, just opens the view
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17844?page=com.atlassian.jira.plugi... ]
Martin Malina closed JBIDE-17844.
---------------------------------
Cannot replicate. Closing.
> Server –> Show in JMX Navigator does not show the server, just opens the view
> -----------------------------------------------------------------------------
>
> Key: JBIDE-17844
> URL: https://issues.jboss.org/browse/JBIDE-17844
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jmx, server
> Affects Versions: 4.2.0.Beta3
> Environment: JBDS 8.0.0.Beta3 B172
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.2.1.CR1
>
>
> When you start a server and then right-click it in the server view and select Show in JMX Navigator, the JMX Navigator view will be opened for you and you will be taken there, but you will only be shown the 3 top level elements.
> You should really be taken straight to the given server in that view. And possibly even connect to it - right now it stays disconnected.
> Interesting is that when you do it again, you will be taken to the server correctly.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 8 months
[JBoss JIRA] (JBIDE-17844) Server –> Show in JMX Navigator does not show the server, just opens the view
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17844?page=com.atlassian.jira.plugi... ]
Martin Malina resolved JBIDE-17844.
-----------------------------------
Resolution: Out of Date
I can confirm that this is no longer applicable in JBDS 8.0.1.CR1 B333. Resolving.
> Server –> Show in JMX Navigator does not show the server, just opens the view
> -----------------------------------------------------------------------------
>
> Key: JBIDE-17844
> URL: https://issues.jboss.org/browse/JBIDE-17844
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jmx, server
> Affects Versions: 4.2.0.Beta3
> Environment: JBDS 8.0.0.Beta3 B172
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.2.1.Final
>
>
> When you start a server and then right-click it in the server view and select Show in JMX Navigator, the JMX Navigator view will be opened for you and you will be taken there, but you will only be shown the 3 top level elements.
> You should really be taken straight to the given server in that view. And possibly even connect to it - right now it stays disconnected.
> Interesting is that when you do it again, you will be taken to the server correctly.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 8 months
[JBoss JIRA] (JBIDE-18819) When discovery URL is not set, "Software/Updates" page is silently hidden
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18819?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-18819:
----------------------------------------
It's not an exception, it's a guard: https://github.com/jbosstools/jbosstools-central/blob/master/central/plug...
Just removing it might be sufficient.
> When discovery URL is not set, "Software/Updates" page is silently hidden
> -------------------------------------------------------------------------
>
> Key: JBIDE-18819
> URL: https://issues.jboss.org/browse/JBIDE-18819
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: central
> Affects Versions: 4.2.0.Final
> Reporter: Mickael Istria
> Assignee: Mickael Istria
> Fix For: 4.2.1.CR1, 4.3.0.Alpha1
>
>
> With latest CI build (in http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio.product_8.... ), Central editor seems to miss the "Software/Updates" tab.
> Log mentions an error, which doesn't seem related at first sight:
> {code:none}
> !SESSION 2014-11-21 15:51:47.555 -----------------------------------------------
> eclipse.buildId=unknown
> java.version=1.8.0_11
> java.vendor=Oracle Corporation
> BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
> Framework arguments: -product com.jboss.devstudio.core.product
> Command-line arguments: -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product
> !ENTRY org.jboss.tools.project.examples 4 0 2014-11-21 15:53:24.762
> !MESSAGE All attempts to discover connectors have failed
> !SUBENTRY 1 org.eclipse.mylyn.discovery.core 4 0 2014-11-21 15:53:24.762
> !MESSAGE Failed to get connectors from RemoteProxyWizardDiscoveryStrategy
> !STACK 0
> java.lang.NullPointerException
> at java.net.URI$Parser.parse(URI.java:3042)
> at java.net.URI.<init>(URI.java:588)
> at org.jboss.tools.project.examples.internal.discovery.xpl.RemoteExternalBundleDiscoveryStrategy.loadRegistry(RemoteExternalBundleDiscoveryStrategy.java:90)
> at org.jboss.tools.project.examples.internal.discovery.xpl.ExternalBundleDiscoveryStrategy.performDiscovery(ExternalBundleDiscoveryStrategy.java:117)
> at org.jboss.tools.project.examples.internal.discovery.ChainedDiscoveryStrategy.performDiscovery(ChainedDiscoveryStrategy.java:62)
> at org.eclipse.mylyn.internal.discovery.core.model.ConnectorDiscovery.performDiscovery(ConnectorDiscovery.java:114)
> at org.jboss.tools.central.internal.discovery.wizards.ProxyWizardManager.loadWizards(ProxyWizardManager.java:107)
> at org.jboss.tools.central.internal.discovery.wizards.ProxyWizardUpdateJob.run(ProxyWizardUpdateJob.java:45)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 8 months
[JBoss JIRA] (JBIDE-18820) define how to handle ide.properties and avoid parent pom to always change
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18820?page=com.atlassian.jira.plugi... ]
Mickael Istria edited comment on JBIDE-18820 at 11/25/14 4:59 AM:
------------------------------------------------------------------
{code}[~mickael_istria] I and [~fbricon] did consider adding a jboss tools branding plugin like we have for jbds but A) how do we ensure that is included AND activated when foundation loads its settings ?! B) how do we ensure it is *NOT* active when devstudio is running ?{code}
A) tricky... We need a bundle to provide this ide-config.properties for anything (even tests), so it's difficult to move this plugin downstream. Which components do need these ide-config.properties expect Central? If only Central requires it, then maybe this would be a good/better place to host a JBoss Tools branding plugin with a good ide-config.properties configuration
B) We just don't put it in JBDS. It would be a separate feature that we don't include. In case someone includes 2 different providers for ide-config.properties, we show an error.
was (Author: maxandersen):
[~nickboldt] none of this *requires* it to be in parent pom. Putting this blindly in parent pom makes it forced that *Everything* need to rebuild to get this info. This is why JBIDE-13452 happened, was it not ? The *missing step* here is that foundation was not upversioned/updated - something that would *need* to happen anyway for this to work. So putting it in parent pom changes nothing if foundation plugin is not updated and version bumped.
As you say your self it does not matter that the version is in the parent pom if the foundation plugin is not rebuilt, but the version of the plugin also need to change. Hence the version should just stay near it instead of bubble up as a global value that is listed as something you can rely on in other modules ...which you cannot or rather should not since it is *not* guaranteed to be right unless we are doing a full complete rebuild of *everything*.
[~mickael_istria] I and [~fbricon] did consider adding a jboss tools branding plugin like we have for jbds but A) how do we ensure that is included AND activated when foundation loads its settings ?! B) how do we ensure it is *NOT* active when devstudio is running ?
It is a *false* assumption that just because foundation has a bug fix that it needs to trigger a full rebuild of everything - this is the thing we need to stop depending on. If this is the case then none of this would be an issue.
> define how to handle ide.properties and avoid parent pom to always change
> -------------------------------------------------------------------------
>
> Key: JBIDE-18820
> URL: https://issues.jboss.org/browse/JBIDE-18820
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: build
> Reporter: Max Rydahl Andersen
>
> As illustrated in JBIDE-18806 our current setup of how ide.properties and project versioning are not working or at least we seem to not get it updated right.
> Current workaround applied is that parent pom now again defines the global version even though this is not reliable at all since not all plugins will be rebuilt. (see JBIDE-13452 for earlier attempts on this)
> Opening this jira to make sure we walkthrough and write down which values should be in ide.properties and what level (4.2.0.CR1, 4.2.0 or 4.2. etc), when they get updated (hopefully rarely) and how to avoid parent pom from always having to respin because of a maintanence release.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 8 months
[JBoss JIRA] (JBIDE-18819) When discovery URL is not set, "Software/Updates" page is silently hidden
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18819?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-18819:
---------------------------------------------
as far as I can see this issue is no different than network connections being bad. That should also be protected against and shown a proper warning/error.
And yes for sure - swallowing exceptions is just not okey thus should be logged!
> When discovery URL is not set, "Software/Updates" page is silently hidden
> -------------------------------------------------------------------------
>
> Key: JBIDE-18819
> URL: https://issues.jboss.org/browse/JBIDE-18819
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: central
> Affects Versions: 4.2.0.Final
> Reporter: Mickael Istria
> Assignee: Mickael Istria
> Fix For: 4.2.1.CR1, 4.3.0.Alpha1
>
>
> With latest CI build (in http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio.product_8.... ), Central editor seems to miss the "Software/Updates" tab.
> Log mentions an error, which doesn't seem related at first sight:
> {code:none}
> !SESSION 2014-11-21 15:51:47.555 -----------------------------------------------
> eclipse.buildId=unknown
> java.version=1.8.0_11
> java.vendor=Oracle Corporation
> BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
> Framework arguments: -product com.jboss.devstudio.core.product
> Command-line arguments: -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product
> !ENTRY org.jboss.tools.project.examples 4 0 2014-11-21 15:53:24.762
> !MESSAGE All attempts to discover connectors have failed
> !SUBENTRY 1 org.eclipse.mylyn.discovery.core 4 0 2014-11-21 15:53:24.762
> !MESSAGE Failed to get connectors from RemoteProxyWizardDiscoveryStrategy
> !STACK 0
> java.lang.NullPointerException
> at java.net.URI$Parser.parse(URI.java:3042)
> at java.net.URI.<init>(URI.java:588)
> at org.jboss.tools.project.examples.internal.discovery.xpl.RemoteExternalBundleDiscoveryStrategy.loadRegistry(RemoteExternalBundleDiscoveryStrategy.java:90)
> at org.jboss.tools.project.examples.internal.discovery.xpl.ExternalBundleDiscoveryStrategy.performDiscovery(ExternalBundleDiscoveryStrategy.java:117)
> at org.jboss.tools.project.examples.internal.discovery.ChainedDiscoveryStrategy.performDiscovery(ChainedDiscoveryStrategy.java:62)
> at org.eclipse.mylyn.internal.discovery.core.model.ConnectorDiscovery.performDiscovery(ConnectorDiscovery.java:114)
> at org.jboss.tools.central.internal.discovery.wizards.ProxyWizardManager.loadWizards(ProxyWizardManager.java:107)
> at org.jboss.tools.central.internal.discovery.wizards.ProxyWizardUpdateJob.run(ProxyWizardUpdateJob.java:45)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 8 months