[JBoss JIRA] (JBIDE-24754) Redhat central screen doesnt show due to JS error
by Supriya Bharadwaj (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24754?page=com.atlassian.jira.plugi... ]
Supriya Bharadwaj commented on JBIDE-24754:
-------------------------------------------
Thanks for the review, [~jkopriva].
[~rkratky], can you please publish the RNs? Thanks!
> Redhat central screen doesnt show due to JS error
> -------------------------------------------------
>
> Key: JBIDE-24754
> URL: https://issues.jboss.org/browse/JBIDE-24754
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: central
> Affects Versions: 4.5.0.AM1
> Reporter: Anton Hughes
> Assignee: Josef Kopriva
> Fix For: 4.5.x
>
>
> I am trying to run the latest Jboss Tools (Oxygen) on Ubuntu 17.04.
> h2. Eclipse Version
> Eclipse Java EE IDE for Web Developers.
> Version: Oxygen Release (4.7.0)
> Build id: 20170620-1800
> h2. Stacktrace
> {code:java}
> org.eclipse.swt.SWTException: An exception was raised in JavaScript
> at org.eclipse.swt.browser.WebKit$Webkit2JavascriptEvaluator.evaluate(WebKit.java:1273)
> at org.eclipse.swt.browser.WebKit.evaluate(WebKit.java:1324)
> at org.eclipse.swt.browser.WebBrowser.evaluate(WebBrowser.java:409)
> at org.eclipse.swt.browser.Browser.evaluate(Browser.java:663)
> at org.eclipse.swt.browser.Browser.evaluate(Browser.java:610)
> at org.jboss.tools.central.internal.browser.VersionedBrowser.<init>(VersionedBrowser.java:51)
> at org.jboss.tools.central.editors.GettingStartedHtmlPage.createBrowserSection(GettingStartedHtmlPage.java:188)
> at org.jboss.tools.central.editors.GettingStartedHtmlPage.createFormContent(GettingStartedHtmlPage.java:175)
> at org.eclipse.ui.forms.editor.FormPage.lambda$0(FormPage.java:163)
> at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
> at org.eclipse.ui.forms.editor.FormPage.createPartControl(FormPage.java:163)
> at org.eclipse.ui.forms.editor.FormEditor.pageChange(FormEditor.java:480)
> at org.eclipse.ui.part.MultiPageEditorPart.setActivePage(MultiPageEditorPart.java:1077)
> at org.eclipse.ui.forms.editor.FormEditor.setActivePage(FormEditor.java:614)
> at org.eclipse.ui.forms.editor.SharedHeaderFormEditor.createPages(SharedHeaderFormEditor.java:106)
> at org.eclipse.ui.part.MultiPageEditorPart.createPartControl(MultiPageEditorPart.java:348)
> at org.eclipse.ui.internal.e4.compatibility.CompatibilityPart.createPartControl(CompatibilityPart.java:151)
> at org.eclipse.ui.internal.e4.compatibility.CompatibilityEditor.createPartControl(CompatibilityEditor.java:99)
> at org.eclipse.ui.internal.e4.compatibility.CompatibilityPart.create(CompatibilityPart.java:355)
> 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.processAnnotated(InjectorImpl.java:990)
> at org.eclipse.e4.core.internal.di.InjectorImpl.processAnnotated(InjectorImpl.java:955)
> at org.eclipse.e4.core.internal.di.InjectorImpl.inject(InjectorImpl.java:124)
> at org.eclipse.e4.core.internal.di.InjectorImpl.internalMake(InjectorImpl.java:399)
> at org.eclipse.e4.core.internal.di.InjectorImpl.make(InjectorImpl.java:318)
> at org.eclipse.e4.core.contexts.ContextInjectionFactory.make(ContextInjectionFactory.java:162)
> at org.eclipse.e4.ui.internal.workbench.ReflectionContributionFactory.createFromBundle(ReflectionContributionFactory.java:105)
> at org.eclipse.e4.ui.internal.workbench.ReflectionContributionFactory.doCreate(ReflectionContributionFactory.java:74)
> at org.eclipse.e4.ui.internal.workbench.ReflectionContributionFactory.create(ReflectionContributionFactory.java:56)
> at org.eclipse.e4.ui.workbench.renderers.swt.ContributedPartRenderer.createWidget(ContributedPartRenderer.java:129)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createWidget(PartRenderingEngine.java:997)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:666)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:772)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.access$0(PartRenderingEngine.java:743)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$2.run(PartRenderingEngine.java:737)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createGui(PartRenderingEngine.java:721)
> at org.eclipse.e4.ui.workbench.renderers.swt.StackRenderer.showTab(StackRenderer.java:1289)
> at org.eclipse.e4.ui.workbench.renderers.swt.LazyStackRenderer.lambda$0(LazyStackRenderer.java:68)
> at org.eclipse.e4.ui.services.internal.events.UIEventHandler$1.run(UIEventHandler.java:40)
> at org.eclipse.swt.widgets.Synchronizer.syncExec(Synchronizer.java:233)
> at org.eclipse.ui.internal.UISynchronizer.syncExec(UISynchronizer.java:144)
> at org.eclipse.swt.widgets.Display.syncExec(Display.java:5439)
> at org.eclipse.e4.ui.internal.workbench.swt.E4Application$1.syncExec(E4Application.java:212)
> at org.eclipse.e4.ui.services.internal.events.UIEventHandler.handleEvent(UIEventHandler.java:36)
> at org.eclipse.equinox.internal.event.EventHandlerWrapper.handleEvent(EventHandlerWrapper.java:201)
> at org.eclipse.equinox.internal.event.EventHandlerTracker.dispatchEvent(EventHandlerTracker.java:197)
> at org.eclipse.equinox.internal.event.EventHandlerTracker.dispatchEvent(EventHandlerTracker.java:1)
> at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
> at org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
> at org.eclipse.equinox.internal.event.EventAdminImpl.dispatchEvent(EventAdminImpl.java:135)
> at org.eclipse.equinox.internal.event.EventAdminImpl.sendEvent(EventAdminImpl.java:78)
> at org.eclipse.equinox.internal.event.EventComponent.sendEvent(EventComponent.java:39)
> at org.eclipse.e4.ui.services.internal.events.EventBroker.send(EventBroker.java:52)
> at org.eclipse.e4.ui.internal.workbench.UIEventPublisher.notifyChanged(UIEventPublisher.java:60)
> at org.eclipse.emf.common.notify.impl.BasicNotifierImpl.eNotify(BasicNotifierImpl.java:374)
> at org.eclipse.e4.ui.model.application.ui.impl.ElementContainerImpl.setSelectedElement(ElementContainerImpl.java:173)
> at org.eclipse.e4.ui.internal.workbench.ModelServiceImpl.showElementInWindow(ModelServiceImpl.java:620)
> at org.eclipse.e4.ui.internal.workbench.ModelServiceImpl.bringToTop(ModelServiceImpl.java:584)
> at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.delegateBringToTop(PartServiceImpl.java:768)
> at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.bringToTop(PartServiceImpl.java:401)
> at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.showPart(PartServiceImpl.java:1187)
> at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditor(WorkbenchPage.java:3261)
> at org.eclipse.ui.internal.WorkbenchPage.access$25(WorkbenchPage.java:3176)
> at org.eclipse.ui.internal.WorkbenchPage$10.run(WorkbenchPage.java:3158)
> at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
> at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:3153)
> at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:3117)
> at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:3098)
> at org.jboss.tools.central.JBossCentralActivator.openJBossCentralEditor(JBossCentralActivator.java:437)
> at org.jboss.tools.central.JBossCentralActivator.getJBossCentralEditor(JBossCentralActivator.java:425)
> at org.jboss.tools.central.ShowJBossCentral$2.run(ShowJBossCentral.java:110)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:37)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:182)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4497)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4110)
> 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: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)
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (ERT-525) Docker launch not able to handle debugging C/C++ programs that printf without newlines [EBZ#521211]
by Friendly Jira Robot (JIRA)
Friendly Jira Robot created ERT-525:
---------------------------------------
Summary: Docker launch not able to handle debugging C/C++ programs that printf without newlines [EBZ#521211]
Key: ERT-525
URL: https://issues.jboss.org/browse/ERT-525
Project: Eclipse Release Train
Issue Type: Task
Components: Linux Tools
Reporter: Friendly Jira Robot
Using the CDT Debug in Container support for C/C++ applications, if a simple C application does a printf without a newline, the line may or may not be shown while stepping or running the program inside gdbserver. It appears that the Docker daemon is not reliable in delivering output in such a case and sometimes it turns up too late (e.g. gdbserver and the application are both finished) so it does not appear. Sometimes it shows up after gdbserver and the application is finished. In such a case, a line containing a single LineFeed character is printed in the place it should have been printed in the first place.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBIDE-24780) Creatinng an OpenShift server adapter should suggest placing Web facet on related project(s)
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24780?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-24780:
-------------------------------------
It is absolutely nonsensical to have a c# application with a javaee web facet. This makes absolutely no sense at all. It will enable all sorts of builders and enforce a project structure with stuff like web-inf and meta-inf and all sorts of weird mappings for source to binary folders.
I simply cannot imagine how this is a good idea.
> Creatinng an OpenShift server adapter should suggest placing Web facet on related project(s)
> --------------------------------------------------------------------------------------------
>
> Key: JBIDE-24780
> URL: https://issues.jboss.org/browse/JBIDE-24780
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.5.0.AM2
> Reporter: Mickael Istria
> Assignee: Rob Stryker
> Fix For: 4.5.x
>
>
> I've created an OpenShift Application from Eclipse IDE providing it an Eclipse Project as input.
> Then I tried to create a server adapter for this project. It didn't work initially because the project isn't a Faceted Web project. I had to quit the OpenShift wizard, make the project a faceted one and restart the wizard.
> I would expect the wizard to create a server adapter to suggest and link to a way to make the project associated with the application a web project in Eclipse IDE so it's one less step to understand for users before it works.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBIDE-24783) Update default registry url for cdk 3
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24783?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-24783:
-------------------------------------
I've made this PR to: 1) not use a default for cdk3, 2) log an error if it couldn't be discovered, including what command was run.
This doesn't soilve the issue of allowing a user in the openshift wizard to 'discover' it... which has a lot of issues about it that would require discussion.
https://github.com/jbosstools/jbosstools-openshift/pull/1549/files
> Update default registry url for cdk 3
> -------------------------------------
>
> Key: JBIDE-24783
> URL: https://issues.jboss.org/browse/JBIDE-24783
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk, openshift
> Affects Versions: 4.5.0.AM2
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.5.x
>
>
> Yesterday I started cdk 3 and it seemed to start ok, but was not really ok.
> The registry command didn't really work:
> {code}
> $ ./minishift openshift registry
> No information found for 'service/docker-registry'
> {code}
> The result is that the openshift connection details showed this under Image Registry URL:
> https://hub.openshift.rhel-cdk.10.1.2.2.xip.io
> This seems like the default value for cdk 2. I think we should update the default value for cdk 3. Or is this simply a default value for an openshift connection? In any case, this should use the cdk 3 value.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBIDE-24801) Remove no-cache header for xml schema files
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24801?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-24801:
------------------------------------
PR merged. No idea what it does.
> Remove no-cache header for xml schema files
> -------------------------------------------
>
> Key: JBIDE-24801
> URL: https://issues.jboss.org/browse/JBIDE-24801
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: server, upstream
> Affects Versions: 4.5.0.Final
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.5.1.AM1
>
>
> This is a followup of JBIDE-20610 . In the past we were trying to figure out how to make validation in Eclipse faster. The problem is that xml schema files return no-cache header and so Eclipse needs to fetch them over and over again.
> We tried to solve this on Eclipse side - allow ignoring of the no-cache http header. But why not try to solve this properly on the server side at least where we have control over it? I think there is no reason why request to urls like http://jboss.org/j2ee/dtd/service-ref_4_0.dtd should return no-cache.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBIDE-24801) Remove no-cache header for xml schema files
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24801?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-24801:
-------------------------------
Fix Version/s: 4.5.1.AM1
> Remove no-cache header for xml schema files
> -------------------------------------------
>
> Key: JBIDE-24801
> URL: https://issues.jboss.org/browse/JBIDE-24801
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: server, upstream
> Affects Versions: 4.5.0.Final
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.5.1.AM1
>
>
> This is a followup of JBIDE-20610 . In the past we were trying to figure out how to make validation in Eclipse faster. The problem is that xml schema files return no-cache header and so Eclipse needs to fetch them over and over again.
> We tried to solve this on Eclipse side - allow ignoring of the no-cache http header. But why not try to solve this properly on the server side at least where we have control over it? I think there is no reason why request to urls like http://jboss.org/j2ee/dtd/service-ref_4_0.dtd should return no-cache.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBIDE-24877) CDK 2 detection results in CDK 3 adapter creation
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24877?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-24877:
-------------------------------------
I'm not able to replicate this at all. :|
When I replicate teh above instructions, I end up with 2 different server adapters created: 1 is a CDK 2.x but just has simple name "Container Development Environment". Opening in the editor reveals it is a proper cdk2 server, with vagrantfile location set properly to (base)/cdk/components/rhel/rhel-ose
The second is a cdk3 server adapter with name "Container Development Environment 3". Opening it in the server editor reveals the proper cdk3 UI with ~/.minishift as the folder (thus ignoring the MINISHIFT_HOME flag).
However, a look at the code reveals this is intentional, and that if ~/.minishift exists, it will initialize THAT folder, but not initialize the MINISHIFT_HOME folder. It will add both as runtime paths, though, which can be verified by opening the runtime detection preference page.
But I am 100% unable to replicate ANY cdk3 server adapter with a CDK2 path or a cdk2 server with a minishift path.
[~mmalina] are you able to replicate?
> CDK 2 detection results in CDK 3 adapter creation
> -------------------------------------------------
>
> Key: JBIDE-24877
> URL: https://issues.jboss.org/browse/JBIDE-24877
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk
> Affects Versions: 4.5.1.AM1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Priority: Minor
>
> As described by [~odockal] in JBIDE-24447:
> When you start devstudio and it finds cdk 2 installed inside ../../../cdk/ relative to eclipse's config, it will create a cdk 3 server instead of cdk 2.
> This relative path normally translate to a structure like this:
> $SOME_DIR/devstudio
> $SOME_DIR/cdk/YOUR/CDK/2/SOMEWHERE/INSIDE/HERE
> BUT... this will only happen in a special situation where you have CDK 2 installed where devstudio looks for it (see above) AND you set up the MINISHIFT_HOME env var to point to your CDK 3 home when you start devstudio.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months