[JBoss JIRA] (JBIDE-21038) Software/Update page is not working on Fedora 23 (Beta)
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21038?page=com.atlassian.jira.plugi... ]
Alexey Kazakov commented on JBIDE-21038:
----------------------------------------
[~ldimaggio] yes sure. I just wanted to know if it's 100% reproducible in Fedora 23. Or it's just on Radim's machine.
Because if Software/Update page is not working on any Fedora 23 by default (Final has been released today btw) then it's a blocker.
> Software/Update page is not working on Fedora 23 (Beta)
> -------------------------------------------------------
>
> Key: JBIDE-21038
> URL: https://issues.jboss.org/browse/JBIDE-21038
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.3.0.Final
> Environment: JBDS 9.0.0.GA
> Reporter: Radim Hopp
> Assignee: Snjezana Peco
> Fix For: 4.3.1.Beta1, 4.4.0.Alpha1
>
>
> Recently I upgraded my system to Fedora 23 (beta) and second page of Cetnral (Software/Update) is not working. It is rendered with "Refreshing..." text and carousel (which is not spinning as it should). One processor core goes 100%.
> java version "1.8.0_65"
> gtk3 version 3.18.2
> jstack: http://pastebin.com/a7U02yjt
> Everything is fine with GTK2.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-21027) Central offers to install Early Access content when importing project examples (EA disabled)
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21027?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-21027:
----------------------------------------
[~fbricon] I believe the approach you suggest is more part of JBIDE-20609.
> Central offers to install Early Access content when importing project examples (EA disabled)
> --------------------------------------------------------------------------------------------
>
> Key: JBIDE-21027
> URL: https://issues.jboss.org/browse/JBIDE-21027
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central, project-examples
> Affects Versions: 4.3.0.Final
> Reporter: Alexey Kazakov
> Assignee: Mickael Istria
> Priority: Critical
> Fix For: 4.3.1.Beta1, 4.4.0.Alpha1
>
> Attachments: angular.png
>
>
> 1. Open Central with EA disabled
> 2. Try to import kitchensink-angularjs project example
> 3. AngularJS (EA version) is offered to install:
> !angular.png!
> 4. Press "Download & Install".
> 5. AngularJS is installed without any warning that it's an EA content.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-21005) Node / Bower / npm location should point to the node executable file instead of the parent folder of it
by Ilya Buziuk (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21005?page=com.atlassian.jira.plugi... ]
Ilya Buziuk updated JBIDE-21005:
--------------------------------
Summary: Node / Bower / npm location should point to the node executable file instead of the parent folder of it (was: Node location should point to the node executable file instead of the parent folder of it)
> Node / Bower / npm location should point to the node executable file instead of the parent folder of it
> -------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-21005
> URL: https://issues.jboss.org/browse/JBIDE-21005
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: javascript, javascript-bower
> Affects Versions: 4.3.0.Final
> Reporter: Alexey Kazakov
> Assignee: Ilya Buziuk
> Fix For: 4.4.0.Alpha1
>
>
> Window->Preferences->Java Script tools->Node
> It's confusing that "Node Location" in that preference page is actually references to the parent folder of the executable node file. I would expect "/usr/bin/nodejs" or "C:/.../node.exe" in that field.
> IMO it's confusing and actually not very flexible. Why wouldn't let users to select the executable file itself?
> WDYT?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-21025) hibernate querying nor content assist is broken
by Len DiMaggio (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21025?page=com.atlassian.jira.plugi... ]
Len DiMaggio commented on JBIDE-21025:
--------------------------------------
Seems like an displaying an informative error message would be better for the user than an NPE!
> hibernate querying nor content assist is broken
> -----------------------------------------------
>
> Key: JBIDE-21025
> URL: https://issues.jboss.org/browse/JBIDE-21025
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: hibernate
> Reporter: Max Rydahl Andersen
> Assignee: Koen Aers
> Priority: Blocker
> Fix For: 4.3.1.Beta1, 4.4.0.Alpha1
>
>
> using html5-kitchensink I cannot get basic content assist to work.
> "from Member m where m.|" gives no content assist at all.
> And trying to run the query results in:
> {code}
> java.lang.NullPointerException
> at org.hibernate.cfg.Configuration.buildTypeRegistrations(Configuration.java:1888)
> at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1845)
> at org.jboss.tools.hibernate.runtime.v_4_3.internal.ConfigurationFacadeImpl.buildTargetSessionFactory(ConfigurationFacadeImpl.java:24)
> at org.jboss.tools.hibernate.runtime.common.AbstractConfigurationFacade.buildSessionFactory(AbstractConfigurationFacade.java:169)
> at org.hibernate.console.ConsoleConfiguration$5.execute(ConsoleConfiguration.java:285)
> at org.hibernate.console.execution.DefaultExecutionContext.execute(DefaultExecutionContext.java:63)
> at org.hibernate.console.ConsoleConfiguration.execute(ConsoleConfiguration.java:108)
> at org.hibernate.console.ConsoleConfiguration.buildSessionFactory(ConsoleConfiguration.java:280)
> at org.hibernate.eclipse.console.actions.ExecuteQueryAction.execute(ExecuteQueryAction.java:81)
> at org.hibernate.eclipse.console.actions.ExecuteQueryAction.run(ExecuteQueryAction.java:55)
> at org.eclipse.jface.action.Action.runWithEvent(Action.java:473)
> at org.hibernate.eclipse.console.actions.ExecuteQueryAction.runWithEvent(ExecuteQueryAction.java:59)
> 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$6.handleEvent(ActionContributionItem.java:462)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4230)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1491)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1514)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1499)
> at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1299)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4072)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3698)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1127)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1018)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:654)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:598)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:139)
> 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:669)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:608)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1515)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months