[JBoss JIRA] (JBIDE-25115) Server adapter editor: should inform user that changes in settings are effective after restart only
by Josef Kopriva (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25115?page=com.atlassian.jira.plugi... ]
Josef Kopriva commented on JBIDE-25115:
---------------------------------------
[~adietish] Hi, I have tried to change Publishing settings and Timeouts, editor gets dirty, but new label is not showing, is this behavior intended?
> Server adapter editor: should inform user that changes in settings are effective after restart only
> ---------------------------------------------------------------------------------------------------
>
> Key: JBIDE-25115
> URL: https://issues.jboss.org/browse/JBIDE-25115
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.5.1.AM2
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Priority: Minor
> Labels: openshift_v3, server_adapter_editor, ux
> Fix For: 4.5.1.Final
>
> Attachments: server-adater-editor-warning.png
>
>
> To the noob user it's not obvious that any change in settings to the server adapter (done in the server adapter editor) is only active after restarting the adapter.
> We could
> * add an explanatory label within the editor ("changes in settings are only active once the server adapter is restarted")
> * a dialog popping upon saving that says "changes in settings are only active once the server adapter is restarted"
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 7 months
[JBoss JIRA] (JBIDE-21755) Properties: "Eager-er" loading of the project properties
by Josef Kopriva (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21755?page=com.atlassian.jira.plugi... ]
Josef Kopriva closed JBIDE-21755.
---------------------------------
Closing, project properties are loaded quickly.
Verified in:
Red Hat JBoss Developer Studio
Version: 11.1.0.GA
Build id: GA-v20171026-1022-B1486
Build date: 20171026-1022
> Properties: "Eager-er" loading of the project properties
> --------------------------------------------------------
>
> Key: JBIDE-21755
> URL: https://issues.jboss.org/browse/JBIDE-21755
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Xavier Coulon
> Assignee: Andre Dietisheim
> Priority: Minor
> Labels: openshift_v3, properties
> Fix For: 4.5.1.Final
>
>
> Once I logged in the OpenShift Explorer, if I expand the connection and select my project, all tables on the tabbed properties view are empty. I need to expand the project in the OpenShift Explorer view to trigger a loading which then allows for displaying the data in the properties view. This is somehow confusing because the user may think that the OpenShift project is empty.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 7 months
[JBoss JIRA] (JBIDE-23422) Server Adapter: Node.js debug session is terminated after ~1 minute and browser shows 502 error
by Josef Kopriva (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23422?page=com.atlassian.jira.plugi... ]
Josef Kopriva closed JBIDE-23422.
---------------------------------
Closing, please follow: https://issues.jboss.org/browse/JBIDE-24868
> Server Adapter: Node.js debug session is terminated after ~1 minute and browser shows 502 error
> -----------------------------------------------------------------------------------------------
>
> Key: JBIDE-23422
> URL: https://issues.jboss.org/browse/JBIDE-23422
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: javascript, openshift
> Affects Versions: 4.4.2.AM2
> Environment: windows 10
> Fedora 24
> Reporter: Ilya Buziuk
> Assignee: Jeff MAURY
> Priority: Critical
> Labels: nodejs, openshift_v3, server_adapter
> Fix For: 4.5.1.Final
>
>
> We've found, that when one is debugging (the code is stopeed at breakpoint, stepping through code, inspecting variables, ...) longer than ~1 minute, browser displays error code 502 and the debug session gets terminated. This makes this feature not very useful, because all debugging must be quicker than that timeout.
> The behavior is captured in this screencast: https://youtu.be/BJf7wcPqNmM (note how at the time 0:42 the page is finally loaded (502 error) and the debug session is terminated (in debug view)).
> We were able to reproduce this issue on F24 and Win10 (using CDK and console.engint.openshift.com)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 7 months
[JBoss JIRA] (JBDS-4617) NoClassDefFoundError: org/apache/http/client/cache/HttpCacheStorage
by Pavol Srna (JIRA)
[ https://issues.jboss.org/browse/JBDS-4617?page=com.atlassian.jira.plugin.... ]
Pavol Srna updated JBDS-4617:
-----------------------------
Priority: Critical (was: Major)
> NoClassDefFoundError: org/apache/http/client/cache/HttpCacheStorage
> -------------------------------------------------------------------
>
> Key: JBDS-4617
> URL: https://issues.jboss.org/browse/JBDS-4617
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: central, central-update, cordovasim, rpm
> Affects Versions: 11.1.0.GA
> Environment: RHEL7, devtools 2.1 \[1\] and DevStudio 11.1-0.20171026.1132.el7 installed from snapshot repository \[2\].
> \[1\] http://brewweb.engineering.redhat.com/brewroot/repos/devtools-2.1-rh-ecli...
> \[2\] https://devstudio.redhat.com/11/snapshots/rpms/11/x86_64/
> Reporter: Lukáš Valach
> Assignee: Nick Boldt
> Priority: Critical
> Fix For: 11.1.0.GA
>
> Attachments: Error_dialog.png, rh-eclipse47-devstudio11.1-0.20171026.1132.el7.log.20171030-1600_strict.txt
>
>
> I got this error when I tried to use "Hybrid Mobile (Cordova) Application Project" wizard.
> {code}
> !ENTRY org.eclipse.jface 4 2 2017-10-30 16:41:56.780
> !MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.jface".
> !STACK 0
> java.lang.NoClassDefFoundError: org/apache/http/client/cache/HttpCacheStorage
> at org.eclipse.thym.core.engine.internal.cordova.NpmBasedEngineRepoProvider.getPlatformEngines(NpmBasedEngineRepoProvider.java:61)
> at org.eclipse.thym.core.engine.internal.cordova.NpmBasedEngineRepoProvider.getEngines(NpmBasedEngineRepoProvider.java:51)
> at org.eclipse.thym.core.engine.internal.cordova.CordovaEngineProvider.getDownloadableEngines(CordovaEngineProvider.java:169)
> at org.eclipse.thym.core.engine.internal.cordova.CordovaEngineProvider.initEngineList(CordovaEngineProvider.java:92)
> at org.eclipse.thym.core.engine.internal.cordova.CordovaEngineProvider.getAvailableEngines(CordovaEngineProvider.java:108)
> at org.eclipse.thym.ui.internal.engine.AvailableCordovaEnginesSection.updateAvailableEngines(AvailableCordovaEnginesSection.java:386)
> at org.eclipse.thym.ui.internal.engine.AvailableCordovaEnginesSection.createControl(AvailableCordovaEnginesSection.java:365)
> at org.eclipse.thym.ui.wizard.project.EngineConfigurationPage.createControl(EngineConfigurationPage.java:52)
> at org.eclipse.jface.wizard.Wizard.createPageControls(Wizard.java:176)
> at org.eclipse.jface.wizard.WizardDialog.createPageControls(WizardDialog.java:688)
> at org.eclipse.jface.wizard.WizardDialog.setWizard(WizardDialog.java:1128)
> at org.eclipse.jface.wizard.WizardDialog.updateForPage(WizardDialog.java:1181)
> at org.eclipse.jface.wizard.WizardDialog.lambda$3(WizardDialog.java:1169)
> at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
> at org.eclipse.jface.wizard.WizardDialog.showPage(WizardDialog.java:1169)
> at org.eclipse.ui.internal.dialogs.NewWizardSelectionPage.advanceToNextPageOrFinish(NewWizardSelectionPage.java:71)
> at org.eclipse.ui.internal.dialogs.NewWizardNewPage.lambda$0(NewWizardNewPage.java:348)
> at org.eclipse.jface.viewers.StructuredViewer$1.run(StructuredViewer.java:831)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.ui.internal.JFaceUtil.lambda$0(JFaceUtil.java:44)
> at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:173)
> at org.eclipse.jface.viewers.StructuredViewer.fireDoubleClick(StructuredViewer.java:828)
> at org.eclipse.jface.viewers.AbstractTreeViewer.handleDoubleSelect(AbstractTreeViewer.java:1459)
> at org.eclipse.jface.viewers.StructuredViewer$4.widgetDefaultSelected(StructuredViewer.java:1258)
> at org.eclipse.jface.util.OpenStrategy.fireDefaultSelectionEvent(OpenStrategy.java:249)
> at org.eclipse.jface.util.OpenStrategy.access$0(OpenStrategy.java:247)
> at org.eclipse.jface.util.OpenStrategy$1.handleEvent(OpenStrategy.java:306)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:86)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:5268)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1348)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4522)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4107)
> 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:291)
> at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:92)
> 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.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:55)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:305)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:239)
> 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:487)
> at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:210)
> at org.eclipse.ui.internal.handlers.LegacyHandlerService.executeCommand(LegacyHandlerService.java:390)
> at org.eclipse.ui.internal.actions.CommandAction.runWithEvent(CommandAction.java:151)
> 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:86)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:5268)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1348)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4522)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4107)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$5.run(PartRenderingEngine.java:1150)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1039)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:153)
> at org.eclipse.ui.internal.Workbench.lambda$3(Workbench.java:680)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:594)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:148)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:151)
> 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:653)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:590)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1499)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1472)
> Caused by: java.lang.ClassNotFoundException: org.apache.http.client.cache.HttpCacheStorage cannot be found by org.eclipse.thym.core_2.1.0.201710130741
> at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:484)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:395)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:387)
> at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:150)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> ... 81 more
> !ENTRY org.eclipse.thym.ui 2 0 2017-10-30 16:41:58.735
> !MESSAGE Unable to determine if cordova is available
> !STACK 0
> java.lang.IllegalArgumentException: invalid version "You have been opted out of telemetry. To change this, run: cordova telemetry on.
> 6.4.0": non-numeric "You have been opted out of telemetry"
> at org.osgi.framework.Version.parseInt(Version.java:170)
> at org.osgi.framework.Version.<init>(Version.java:126)
> at org.osgi.framework.Version.valueOf(Version.java:257)
> at org.osgi.framework.Version.parseVersion(Version.java:228)
> at org.eclipse.thym.ui.wizard.project.WizardNewHybridProjectCreationPage$CordovaIsAvailableJob.run(WizardNewHybridProjectCreationPage.java:237)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56)
> Caused by: java.lang.NumberFormatException: For input string: "You have been opted out of telemetry"
> at java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
> at java.lang.Integer.parseInt(Integer.java:580)
> at java.lang.Integer.parseInt(Integer.java:615)
> at org.osgi.framework.Version.parseInt(Version.java:168)
> ... 5 more
> {code}
> Please see also Steps to Reproduce.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 7 months
[JBoss JIRA] (JBIDE-25309) Can't install stuff from RH Central into JBoss Tools
by Lukáš Valach (JIRA)
Lukáš Valach created JBIDE-25309:
------------------------------------
Summary: Can't install stuff from RH Central into JBoss Tools
Key: JBIDE-25309
URL: https://issues.jboss.org/browse/JBIDE-25309
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: central, central-update
Affects Versions: 4.5.1.Final
Environment: RHEL7, OpenJDK 1.8
Reporter: Lukáš Valach
Assignee: Nick Boldt
Priority: Blocker
Fix For: 4.5.1.Final
Attachments: JBT_unavailable_connectors.png, JBT_unavailable_connectors.txt
I can't install stuff from RH Central into JBoss Tools because of unavailable connectors.
There is dialog I got:
!JBT_unavailable_connectors.png|thumbnail!
After click "No" the error dialog with this message was displayed:
[^JBT_unavailable_connectors.txt]
Error message is saying that some features is missing on update site \[1\] but I see that these features present on update site. I chosen one of the connectors and verified that it is possible to install them form update site using Help -> Install New Software -> Add \[1\].
\[1\] http://download.jboss.org/jbosstools/oxygen/staging/updates/
This problem appears only in JBoss Tools, JBDS works fine.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 7 months
[JBoss JIRA] (JBIDE-25192) Error when eclipse environment has MINISHIFT_HOME different from adapter
by Ondrej Dockal (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25192?page=com.atlassian.jira.plugi... ]
Ondrej Dockal commented on JBIDE-25192:
---------------------------------------
[~mmalina] Thanks! Yeah, that is the problem, question here is if we can close this one, as exact steps can be verified, and problem will be fix in JBIDE-25308 or reopen this jira and fix it here and make the other one duplicate. I vote for first option.
> Error when eclipse environment has MINISHIFT_HOME different from adapter
> ------------------------------------------------------------------------
>
> Key: JBIDE-25192
> URL: https://issues.jboss.org/browse/JBIDE-25192
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk
> Affects Versions: 4.5.1.AM3
> Reporter: Rob Stryker
> Assignee: Rob Stryker
> Priority: Critical
> Fix For: 4.5.1.Final
>
>
> Steps to reproduce:
> 1) Start eclipse with an environment that has a MINISHIFT_HOME set to one value
> 2) Create a server adapter with the default minishift home ~/.minishift (ie make no changes)
> 3) via cmdline, try to setup cdk using cdk 3.2a and the .minishift home folder
> 4) Try to start the server
> Expected results: Server starts as expected
> Actual results: No minishift_home is set. The eclipse environment's minishift home is used. The server attempts to start and tells you to call setup-cdk. The user gets very confused, because the server editor clearly is using ~/.minishift as the home.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 7 months