[JBoss JIRA] (JBDS-4619) Unable to access Red Hat Central and update software.
by Josef Kopriva (Jira)
[ https://issues.jboss.org/browse/JBDS-4619?page=com.atlassian.jira.plugin.... ]
Josef Kopriva commented on JBDS-4619:
-------------------------------------
[~fg78nc] Hi, are you experiencing still this issue with newer versions? Thank you!
> Unable to access Red Hat Central and update software.
> -----------------------------------------------------
>
> Key: JBDS-4619
> URL: https://issues.jboss.org/browse/JBDS-4619
> Project: Red Hat CodeReady Studio (devstudio)
> Issue Type: Bug
> Components: central
> Affects Versions: 11.0.0.GA
> Environment: Windows 10
> Proxy server
> Reporter: Farid Guliyev
> Assignee: Jeff MAURY
> Priority: Major
> Fix For: 12.x
>
>
> Red Hat Central page is not loading.
> Getting the following error on Help -> Check for updates
> Unable to read repository at https://devstudio.redhat.com/11/stable/updates/content.xml.
> sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
> I am getting those errors on startup as well:
> An internal error occurred during: "Download quickstarts list".
> An internal error occurred during: "Extract Central page".
> An internal error occurred during: "Refreshing JBoss Buzz...".
> ide-config.properties can't be loaded from the org.jboss.tools.foundation.core plugin
> log info :
> !ENTRY org.jboss.tools.foundation.core 4 0 2017-11-02 16:09:38.463
> !MESSAGE Unable to load properties from http://download.jboss.org/jbosstools/configuration/ide-config.properties. Falling back on embedded properties
> !STACK 1
> org.eclipse.core.runtime.CoreException: Unable to retrieve properties from http://download.jboss.org/jbosstools/configuration/ide-config.properties
> at org.jboss.tools.foundation.core.properties.internal.VersionPropertiesProvider.loadProperties(VersionPropertiesProvider.java:276)
> at org.jboss.tools.foundation.core.properties.internal.VersionPropertiesProvider.getValue(VersionPropertiesProvider.java:151)
> at org.jboss.tools.foundation.core.properties.internal.VersionPropertiesProvider.getValue(VersionPropertiesProvider.java:217)
> at org.jboss.tools.central.installation.InstallationChecker.<init>(InstallationChecker.java:55)
> at org.jboss.tools.central.installation.InstallationChecker.getInstance(InstallationChecker.java:84)
> at org.jboss.tools.central.installation.CentralInstallationPage.createControl(CentralInstallationPage.java:52)
> at org.eclipse.ui.internal.about.InstallationDialog.tabSelected(InstallationDialog.java:247)
> at org.eclipse.ui.internal.about.InstallationDialog.lambda$1(InstallationDialog.java:232)
> at org.eclipse.swt.events.SelectionListener$1.widgetSelected(SelectionListener.java:81)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:249)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:86)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4428)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1079)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4238)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3817)
> 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.dialogs.AboutDialog.lambda$0(AboutDialog.java:128)
> at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
> at org.eclipse.ui.internal.dialogs.AboutDialog.buttonPressed(AboutDialog.java:124)
> at org.eclipse.jface.dialogs.Dialog.lambda$0(Dialog.java:619)
> at org.eclipse.swt.events.SelectionListener$1.widgetSelected(SelectionListener.java:81)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:249)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:86)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4428)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1079)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4238)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3817)
> 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.about.AboutHandler.execute(AboutHandler.java:28)
> 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:497)
> 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:4428)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1079)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4238)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3817)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$5.run(PartRenderingEngine.java:1155)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1044)
> 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:497)
> 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)
> !SUBENTRY 1 org.jboss.tools.foundation.core 4 0 2017-11-02 16:09:38.463
> !MESSAGE Unable to retrieve properties from http://download.jboss.org/jbosstools/configuration/ide-config.properties
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 4 months
[JBoss JIRA] (ERT-746) [GTK] DateTime drop-down popup shell does not hiding on focus lost [EBZ#547811]
by Eric Williams (Jira)
[ https://issues.jboss.org/browse/ERT-746?page=com.atlassian.jira.plugin.sy... ]
Eric Williams reassigned ERT-746:
---------------------------------
Sprint: devex #170 Aug 2019
Assignee: Eric Williams
> [GTK] DateTime drop-down popup shell does not hiding on focus lost [EBZ#547811]
> -------------------------------------------------------------------------------
>
> Key: ERT-746
> URL: https://issues.jboss.org/browse/ERT-746
> Project: Eclipse Release Train
> Issue Type: Task
> Components: Platform
> Reporter: Friendly Jira Robot
> Assignee: Eric Williams
> Priority: Major
> Labels: SWT, bzira
>
> Debian Stretch
> GTK 3.22.30
> Eclipse SDK 4.12M3.
> When DateTime losts focus or when moving shell, drop down popup does not dissappear.
> It also reflects on GTK2 on SWT 3.108.
> It appears on the main shell of the application, but it does not appear on sub shell with style SWT.ON_TOP.
> If we comment the string DateTime.java:517 (handleFocus(SWT.FocusOut);) everything works fine. But i don't what this popupFilter needs for.
> I also attached snippet and video which reproduce the problem.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 4 months
[JBoss JIRA] (ERT-745) [StyledText] Support disabled look in StyledText widget [EBZ#4745]
by Eric Williams (Jira)
[ https://issues.jboss.org/browse/ERT-745?page=com.atlassian.jira.plugin.sy... ]
Eric Williams reassigned ERT-745:
---------------------------------
Sprint: devex #170 Aug 2019
Assignee: Eric Williams
> [StyledText] Support disabled look in StyledText widget [EBZ#4745]
> ------------------------------------------------------------------
>
> Key: ERT-745
> URL: https://issues.jboss.org/browse/ERT-745
> Project: Eclipse Release Train
> Issue Type: Task
> Components: Platform
> Reporter: Friendly Jira Robot
> Assignee: Eric Williams
> Priority: Major
> Labels: 4.13, SWT, bzira
>
> To see the problem, launch the Control example and go to the Text tab.
> Toggle the Enabled flag to off.
> Notice that the Text widget looks disabled but not the StyledText one.
> (it's labeled as RichText -- has been fixed in Eclipse View copy of Controls Example)
> For consistency, I think we should supply a Disabled look for StyledText.
> NOTES:
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 4 months
[JBoss JIRA] (JBIDE-26751) Content Assist item in the Edit menu is missing when cursor is placed between the angle brackets ('<' and '>') in the beans.xml (CDI project) file
by Zbyněk Červinka (Jira)
[ https://issues.jboss.org/browse/JBIDE-26751?page=com.atlassian.jira.plugi... ]
Zbyněk Červinka commented on JBIDE-26751:
-----------------------------------------
[~odockal]
*Red Hat CodeReady Studio*
Version: 12.13.0.AM1
Build id: AM1-v20190720-1320-B4681
Build date: 20190720-1320
> Content Assist item in the Edit menu is missing when cursor is placed between the angle brackets ('<' and '>') in the beans.xml (CDI project) file
> --------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-26751
> URL: https://issues.jboss.org/browse/JBIDE-26751
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdi
> Environment: OS X 10.14.6
> Reporter: Zbyněk Červinka
> Priority: Major
> Attachments: example_of_context_menu_which_is_present.png, missing_context_menu.png
>
>
> When running the BeansXMLCompletionTestCDI20.class, the Content Assist item in the Edit menu is being checked. See the "missing_context_menu.png" image in the attachment to see the situation and the missing Content Assist item in the Edit menu. Then see the "example_of_context_menu_which_is_present.png" - here is captured the situation where the Content Assist item is present.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 4 months
[JBoss JIRA] (JBIDE-26751) Content Assist item in the Edit menu is missing when cursor is placed between the angle brackets ('<' and '>') in the beans.xml (CDI project) file
by Ondrej Dockal (Jira)
[ https://issues.jboss.org/browse/JBIDE-26751?page=com.atlassian.jira.plugi... ]
Ondrej Dockal commented on JBIDE-26751:
---------------------------------------
[~zcervink] What version of codereadystudio was this reproduced on?
> Content Assist item in the Edit menu is missing when cursor is placed between the angle brackets ('<' and '>') in the beans.xml (CDI project) file
> --------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-26751
> URL: https://issues.jboss.org/browse/JBIDE-26751
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdi
> Environment: OS X 10.14.6
> Reporter: Zbyněk Červinka
> Priority: Major
> Attachments: example_of_context_menu_which_is_present.png, missing_context_menu.png
>
>
> When running the BeansXMLCompletionTestCDI20.class, the Content Assist item in the Edit menu is being checked. See the "missing_context_menu.png" image in the attachment to see the situation and the missing Content Assist item in the Edit menu. Then see the "example_of_context_menu_which_is_present.png" - here is captured the situation where the Content Assist item is present.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 4 months
[JBoss JIRA] (JBIDE-26740) add option to Wildfly-Overview to "auto-restart" after publishing
by nimo stephan (Jira)
[ https://issues.jboss.org/browse/JBIDE-26740?page=com.atlassian.jira.plugi... ]
nimo stephan edited comment on JBIDE-26740 at 7/26/19 6:20 PM:
---------------------------------------------------------------
Could you make a FR (Feature Request) at the WTP level, as you are better involved in this and know what has to be changed.
It makes sense that "Every change in deployment should trigger a wildfly restart automatically."..especially while developing. Having an option for this would be good. Doing the restart manually is awkward..
was (Author: nimo22):
Could you make a FR (Feature Request) at the WTP level, as you are better involved in this and know what has to be changed.
It makes sense that "Every change in deployment should trigger a wildfly restart automatically." Having an option for this would be good. Doing the restart manually is awkward..
> add option to Wildfly-Overview to "auto-restart" after publishing
> -----------------------------------------------------------------
>
> Key: JBIDE-26740
> URL: https://issues.jboss.org/browse/JBIDE-26740
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: server
> Affects Versions: 4.12.0.Final
> Reporter: nimo stephan
> Priority: Critical
>
> Actually, with *Jboss Tools* we can change to automatically *publish* to Wildfly-Server after resources has changed. However, it makes sense *to restart the server automatically* after code/resource is changed and published.
> Please add a new option in "Wildfly Server Overview" beneath the "Publishing" called "*Restarting*" with a checkbox. So when user checks "restart after publish", *server will be automatically restarted* after resources has changed.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 4 months