[JBoss JIRA] (DEVTOOLS-3) Update/Refresh SWT Documentation
by Leo Ufimtsev (JIRA)
[ https://issues.jboss.org/browse/DEVTOOLS-3?page=com.atlassian.jira.plugin... ]
Leo Ufimtsev updated DEVTOOLS-3:
--------------------------------
Sprint: devex #139 October 2017
> Update/Refresh SWT Documentation
> --------------------------------
>
> Key: DEVTOOLS-3
> URL: https://issues.jboss.org/browse/DEVTOOLS-3
> Project: Developer Tools Team (IDE)
> Issue Type: Task
> Reporter: Leo Ufimtsev
> Assignee: Leo Ufimtsev
> Labels: swt
>
> During the Eclipse conference, a number of users complained that it is hard to figure out how to get started with SWT, how to contribute etc..
> Current documentation has a lot of sections that are out of date, (e.g win XP screen shots).
> The documentation needs to be consolidated, reduced, simplified, upated and made more clear.
> It might be beneficial to track visitors to documentation page also maybe.. .
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 6 months
[JBoss JIRA] (DEVTOOLS-3) Update/Refresh SWT Documentation
by Leo Ufimtsev (JIRA)
[ https://issues.jboss.org/browse/DEVTOOLS-3?page=com.atlassian.jira.plugin... ]
Leo Ufimtsev reassigned DEVTOOLS-3:
-----------------------------------
Assignee: Leo Ufimtsev
> Update/Refresh SWT Documentation
> --------------------------------
>
> Key: DEVTOOLS-3
> URL: https://issues.jboss.org/browse/DEVTOOLS-3
> Project: Developer Tools Team (IDE)
> Issue Type: Task
> Reporter: Leo Ufimtsev
> Assignee: Leo Ufimtsev
> Labels: swt
>
> During the Eclipse conference, a number of users complained that it is hard to figure out how to get started with SWT, how to contribute etc..
> Current documentation has a lot of sections that are out of date, (e.g win XP screen shots).
> The documentation needs to be consolidated, reduced, simplified, upated and made more clear.
> It might be beneficial to track visitors to documentation page also maybe.. .
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 6 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:
-----------------------------
Workaround Description:
Install from jar instead of rpm.
{code}
java -jar devstudio-11.1.0.GA-installer-standalone.jar
{code}
Workaround: Workaround Exists
> 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, hma-wizard-stuck.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, 6 months
[JBoss JIRA] (JBIDE-24969) Add platform events to usage reporting
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24969?page=com.atlassian.jira.plugi... ]
Jeff MAURY reassigned JBIDE-24969:
----------------------------------
Assignee: Jeff MAURY
> Add platform events to usage reporting
> --------------------------------------
>
> Key: JBIDE-24969
> URL: https://issues.jboss.org/browse/JBIDE-24969
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: usage
> Affects Versions: 4.5.0.Final
> Reporter: Jeff MAURY
> Assignee: Jeff MAURY
> Labels: usage
> Fix For: 4.5.x
>
>
> In addition to the jbosstools events reported, we should benefits from the events emitted by the Eclipse platform and send them to the usage reporting feature.
> Those events may be:
> * perspective events
> * view events
> * editor events
> * menu events
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 6 months
[JBoss JIRA] (JBIDE-25309) Can't install stuff from RH Central into JBoss Tools
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25309?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-25309:
------------------------------------
Generally I use the label releasework to identify things that will be resolved as part of the release, rather than before it, and use the fixversion of the release. But as I'll be on PTO on GA announcement day, I'm fine with resolving this for 4.5.2.AM1 instead.
> 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
> Labels: releasework
> Fix For: 4.5.2.AM1
>
> Attachments: JBT_unavailable_connectors.png, JBT_unavailable_connectors.txt, central-451final-works-fine.png, what-the-what.png
>
>
> 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, 6 months
[JBoss JIRA] (JBIDE-25309) Can't install stuff from RH Central into JBoss Tools
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25309?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-25309:
-------------------------------
Labels: releasework (was: )
> 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
> Labels: releasework
> Fix For: 4.5.2.AM1
>
> Attachments: JBT_unavailable_connectors.png, JBT_unavailable_connectors.txt, central-451final-works-fine.png, what-the-what.png
>
>
> 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, 6 months
[JBoss JIRA] (JBIDE-25309) Can't install stuff from RH Central into JBoss Tools
by Pavol Srna (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25309?page=com.atlassian.jira.plugi... ]
Pavol Srna commented on JBIDE-25309:
------------------------------------
I've set the fix version to 4.5.2.AM1 to confirm the problem is gone. Not a blocker for 4.5.1.Final.
> 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
> Fix For: 4.5.2.AM1
>
> Attachments: JBT_unavailable_connectors.png, JBT_unavailable_connectors.txt, central-451final-works-fine.png, what-the-what.png
>
>
> 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, 6 months
[JBoss JIRA] (JBIDE-25309) Can't install stuff from RH Central into JBoss Tools
by Pavol Srna (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25309?page=com.atlassian.jira.plugi... ]
Pavol Srna updated JBIDE-25309:
-------------------------------
Fix Version/s: 4.5.2.AM1
(was: 4.5.1.Final)
> 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
> Fix For: 4.5.2.AM1
>
> Attachments: JBT_unavailable_connectors.png, JBT_unavailable_connectors.txt, central-451final-works-fine.png, what-the-what.png
>
>
> 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, 6 months
[JBoss JIRA] (JBIDE-25309) Can't install stuff from RH Central into JBoss Tools
by Pavol Srna (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25309?page=com.atlassian.jira.plugi... ]
Pavol Srna commented on JBIDE-25309:
------------------------------------
I didn't manage to install in bulk. However installing in groups one by one worked for me. This probably implies (as Nick is saying) a server/network issue not an issue in the tooling.
> 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
> Fix For: 4.5.1.Final
>
> Attachments: JBT_unavailable_connectors.png, JBT_unavailable_connectors.txt, central-451final-works-fine.png, what-the-what.png
>
>
> 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, 6 months