[JBoss JIRA] (JBIDE-2720) Need 64-bit windows support
by Carsten Pfeiffer (JIRA)
[ https://issues.jboss.org/browse/JBIDE-2720?page=com.atlassian.jira.plugin... ]
Carsten Pfeiffer commented on JBIDE-2720:
-----------------------------------------
We had a holiday in Germany yesterday. I'll try the Eclipse changes today and report back. Then I'll make the patches available, and ideally get them maintained at mozilla-x86-64.com. Mozilla is using mercurial, so I cannot easily create a full mozilla repo together with the patches at github.
> Need 64-bit windows support
> ---------------------------
>
> Key: JBIDE-2720
> URL: https://issues.jboss.org/browse/JBIDE-2720
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: Visual Page Editor core
> Affects Versions: 2.1.0.GA, 2.1.1, 2.1.2, 3.0.0.alpha
> Reporter: Samuel Mendenhall
> Assignee: Yahor Radtsevich
> Fix For: 4.0.x
>
> Attachments: .mozconfig, buildlog1.log, buildlog1_x86_short.log, buildlog2.log, buildlog2_x86_short.log, buildlog3.log, build_error_when_run_x64.bat.txt, build_log_win_sdk6.log.txt, build_log_win_sdk7.log.txt, mozconfig1, mozconfig2
>
>
> If you use a 64 bit jdk, the XULRunner parts of JBoss Tools does not load.
> We should look into providing a xulrunner for windows 64 bit.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 11 months
[JBoss JIRA] (JBDS-1659) If set as default, java 1.5 is used even if 1.6 is chosen during installation
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBDS-1659?page=com.atlassian.jira.plugin.... ]
Martin Malina commented on JBDS-1659:
-------------------------------------
I would think so - Java 1.5 hasn't been provided in the last few releases of OS X. And even if they got it from somewhere, there's very little chance they would have it as their default jdk - especially since the Java Preferences app is gone. So +1 from me.
> If set as default, java 1.5 is used even if 1.6 is chosen during installation
> -----------------------------------------------------------------------------
>
> Key: JBDS-1659
> URL: https://issues.jboss.org/browse/JBDS-1659
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: installer
> Affects Versions: 4.1.0.M1, 5.0.0.GA
> Environment: jbdevstudio-product-macosx-cocoa-x86_64-4.1.0.v201105091943R-H400-M1.jar
> Mac OS X 10.5 Leopard
> Reporter: Martin Malina
> Assignee: Denis Golovin
> Priority: Critical
> Fix For: 7.0.x
>
> Attachments: screenshot69.png, screenshot70.png
>
>
> If java 1.5 is set as default in the Java Preferences utility and you select java 1.6 during JBDS installation, it is still started with 1.5.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 11 months
[JBoss JIRA] (JBDS-2624) Content of JBDS update site shows Usage and Common Mylyn feature as available for installation from core category
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-2624?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen commented on JBDS-2624:
-------------------------------------------
JBoss tools usage -> just move to uncategorized since no need lock down the specific usage feature.
Mylyn -> is not part of core, so put it just under application development.
> Content of JBDS update site shows Usage and Common Mylyn feature as available for installation from core category
> -----------------------------------------------------------------------------------------------------------------
>
> Key: JBDS-2624
> URL: https://issues.jboss.org/browse/JBDS-2624
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: updatesite
> Affects Versions: 7.0.0.Alpha2
> Reporter: Denis Golovin
> Priority: Trivial
> Attachments: InstallContentAfterRunningUniversalInstaller.png
>
>
> After installation Eclipse Install dialog looks like:
> !InstallContentAfterRunningUniversalInstaller.png!
> These two features should not be visible after installation:
> 1. Usage Feature - should be included into JBDS product feature
> 2. Common Mylyn - should be uncategorised, because it doesn't provide any visible functionality for user and it is installed when Mylyn Issue Tracker Connector installed out of central.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 11 months
[JBoss JIRA] (JBDS-2626) Use TP for central
by Max Rydahl Andersen (JIRA)
Max Rydahl Andersen created JBDS-2626:
-----------------------------------------
Summary: Use TP for central
Key: JBDS-2626
URL: https://issues.jboss.org/browse/JBDS-2626
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Reporter: Max Rydahl Andersen
As discovered in JBDS-2486 the current mechanism for mirroring and setup of central is spread across build.xml's and no reliable way to reproduce nor validate a site.
Suggestion is to do "dumb" mirrors which is then used together with a TP with specific IU's + versions.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 11 months
[JBoss JIRA] (JBIDE-2720) Need 64-bit windows support
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-2720?page=com.atlassian.jira.plugin... ]
Max Rydahl Andersen commented on JBIDE-2720:
--------------------------------------------
[~carsten.pfeiffer] seems eclipse already reacted so I assume next step is to try your patch ?
is it available in github somewhere ?
> Need 64-bit windows support
> ---------------------------
>
> Key: JBIDE-2720
> URL: https://issues.jboss.org/browse/JBIDE-2720
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: Visual Page Editor core
> Affects Versions: 2.1.0.GA, 2.1.1, 2.1.2, 3.0.0.alpha
> Reporter: Samuel Mendenhall
> Assignee: Yahor Radtsevich
> Fix For: 4.0.x
>
> Attachments: .mozconfig, buildlog1.log, buildlog1_x86_short.log, buildlog2.log, buildlog2_x86_short.log, buildlog3.log, build_error_when_run_x64.bat.txt, build_log_win_sdk6.log.txt, build_log_win_sdk7.log.txt, mozconfig1, mozconfig2
>
>
> If you use a 64 bit jdk, the XULRunner parts of JBoss Tools does not load.
> We should look into providing a xulrunner for windows 64 bit.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 11 months
[JBoss JIRA] (JBIDE-14356) GC overhead limit exceeded when adding fileset to LiveReload Server
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14356?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen reassigned JBIDE-14356:
-------------------------------------------
Assignee: Rob Stryker
Stian - thanks for the bugreport - livereload server shouldn't have this fileset enabled; it doesn't make sense for it since it has no local files. (But I understand why you could misunderstand it as being the fileset to setup - thats not nice)
Rob - could you look at why this is happening ?
and how to remove fileset for server types where fileset does not make sense ?
> GC overhead limit exceeded when adding fileset to LiveReload Server
> -------------------------------------------------------------------
>
> Key: JBIDE-14356
> URL: https://issues.jboss.org/browse/JBIDE-14356
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: livereload
> Reporter: Stian Thorgersen
> Assignee: Rob Stryker
>
> When creating a LiveReload Server and adding a fileset Eclipse hangs consuming a lot of CPU. Eventually the error message "Unhandled event loop exception / GC overhead limit exceeded" is displayed.
> From the stack trace while this is going the only interesting thread is:
> {code}
> "main" prio=10 tid=0x00007ff9a0009800 nid=0x22c2 runnable [0x00007ff9a81fe000]
> java.lang.Thread.State: RUNNABLE
> at org.eclipse.swt.internal.gtk.OS._gtk_main_do_event(Native Method)
> at org.eclipse.swt.internal.gtk.OS.gtk_main_do_event(OS.java:8654)
> at org.eclipse.swt.widgets.Display.eventProc(Display.java:1243)
> at org.eclipse.swt.internal.gtk.OS._g_main_context_iteration(Native Method)
> at org.eclipse.swt.internal.gtk.OS.g_main_context_iteration(OS.java:2283)
> at org.eclipse.swt.widgets.Shell.setVisible(Shell.java:2153)
> at org.eclipse.swt.widgets.Shell.open(Shell.java:1546)
> at org.eclipse.jface.window.Window.open(Window.java:798)
> at org.eclipse.ui.internal.statushandlers.InternalDialog.open(InternalDialog.java:327)
> at org.eclipse.ui.internal.statushandlers.WorkbenchStatusDialogManagerImpl.doAddStatusAdapter(WorkbenchStatusDialogManagerImpl.java:270)
> at org.eclipse.ui.internal.statushandlers.WorkbenchStatusDialogManagerImpl.addStatusAdapter(WorkbenchStatusDialogManagerImpl.java:197)
> at org.eclipse.ui.statushandlers.WorkbenchStatusDialogManager.addStatusAdapter(WorkbenchStatusDialogManager.java:156)
> at org.eclipse.ui.statushandlers.WorkbenchErrorHandler.showStatusAdapter(WorkbenchErrorHandler.java:101)
> at org.eclipse.ui.statushandlers.WorkbenchErrorHandler.handle(WorkbenchErrorHandler.java:57)
> at org.eclipse.ui.internal.ide.IDEWorkbenchErrorHandler.handle(IDEWorkbenchErrorHandler.java:106)
> at org.eclipse.ui.internal.WorkbenchErrorHandlerProxy.handle(WorkbenchErrorHandlerProxy.java:36)
> at org.eclipse.ui.statushandlers.StatusManager.handle(StatusManager.java:189)
> at org.eclipse.ui.statushandlers.StatusManager.handle(StatusManager.java:231)
> at org.eclipse.ui.statushandlers.StatusManager.handle(StatusManager.java:242)
> at org.eclipse.ui.application.WorkbenchAdvisor.eventLoopException(WorkbenchAdvisor.java:326)
> at org.eclipse.ui.internal.ExceptionHandler.handleException(ExceptionHandler.java:65)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:830)
> at org.eclipse.jface.window.Window.open(Window.java:802)
> at org.jboss.ide.eclipse.archives.webtools.filesets.FilesetActionProvider$1.run(FilesetActionProvider.java:202)
> at org.eclipse.jface.action.Action.runWithEvent(Action.java:499)
> at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584)
> at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501)
> at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:411)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1392)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3717)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3338)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1108)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:992)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:137)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:600)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:555)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:354)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:181)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:636)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1450)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1426)
> {code}
> I'm running:
> * Eclipse Kepler M6 with JBoss Tools 4.1 Alpha 2
> * OpenJDK 1.7.0_21
> * Ubuntu 13.04
> To reproduce create a new LiveReload server. Expand it, right click on 'Filesets' and select 'Create New File Filter'. Then write '/' in 'Root Directory'. Observe that Eclipse now consumes ~100% cpu on all available cores. Wait for a few minutes and the error message mentioned earlier should be displayed
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 11 months
[JBoss JIRA] (JBIDE-13879) BrowserSim to show deployed app when click Run BrowerSim icon
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13879?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen updated JBIDE-13879:
----------------------------------------
Priority: Critical (was: Major)
> BrowserSim to show deployed app when click Run BrowerSim icon
> -------------------------------------------------------------
>
> Key: JBIDE-13879
> URL: https://issues.jboss.org/browse/JBIDE-13879
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: browsersim
> Affects Versions: 4.0.0.Final
> Reporter: Michelle Murray
> Assignee: Yahor Radtsevich
> Priority: Critical
> Fix For: 4.1.0.Beta1
>
>
> I deployed a simple dynamic web app to an EAP server.
> To view the deployed app (http://localhost:8080/testing/ say) with BrowserSim I can do two things:
> 1) Show the deployed app in a standard browser (In Servers tab, right-click on app then Show In > Web Browser), click in the tab of the opened web browser and then click the Run BrowserSim icon.
> 2) Change the default browser to BrowserSim (Window > Web Browser > BrowserSim) and then open the app in web browser (In Servers tab, right-click on app then Show In > Web Browser).
> It would be great if this could be simplified and a third and fourth option added:
> 3) Select the deployed app in the Servers tab and then click the Run BrowserSim icon. [At the moment this sequence runs BrowserSim but the displayed page is 'about:blank' and not the deployed app.]
> 4) Right-click the deployed app in the Servers tab and click Show In > BrowserSim.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 11 months
[JBoss JIRA] (JBIDE-14079) Weinre in browsersim slow/not-informative
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14079?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen updated JBIDE-14079:
----------------------------------------
Priority: Minor (was: Major)
> Weinre in browsersim slow/not-informative
> -----------------------------------------
>
> Key: JBIDE-14079
> URL: https://issues.jboss.org/browse/JBIDE-14079
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: browsersim
> Reporter: Max Rydahl Andersen
> Assignee: Konstantin Marmalyukov
> Priority: Minor
> Fix For: 4.1.0.Beta1
>
>
> BrowerSim weinre seems to load *very* slowly and there is just a big white dialog shown while it do so.
> I initially thought it was broken but after 4-5 attempts it suddenly showed up.
> Problem is users has no idea what is actually going on.
> Could we:
> A) show a progress monitor (even a fake one would be useful)
> B) show what url the dialog is visiting (that gives a hint it is waiting)
> C) have a link/info button explaining you can configure weinre in preferences
> Ca) have a dialog pop up on initial start of weinre explaining it will inject weinre and go to client url X which can be configured in the preferences...and then a "Do not ask me again" checkbox for future usage.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 11 months