[JBoss JIRA] (JBIDE-16132) XCode library search path is not set properly
by Gorkem Ercan (JIRA)
Gorkem Ercan created JBIDE-16132:
------------------------------------
Summary: XCode library search path is not set properly
Key: JBIDE-16132
URL: https://issues.jboss.org/browse/JBIDE-16132
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: aerogear-hybrid
Affects Versions: 4.1.1.CR1
Reporter: Gorkem Ercan
Priority: Critical
Fix For: 4.1.1.CR1
If a Cordova plugin adds a custom framework as a dependency for iOS the project fails to run and the exported XCode project does not compile.
This is because the iOS project generator does not set the library search paths properly for custom frameworks.
Aerogear Push Plugin now uses such a framework.
--
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, 4 months
[JBoss JIRA] (JBIDE-15313) Investigate how to handle Wildfly port multiplexing
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15313?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-15313:
-------------------------------------
News so far:
1) The api we currently use (ModelControllerClient.Factory.create(etc)) has a signature that allows the protocol to be passed in, so if we can discover the protocol (or allow the user to set it) it can work
2) Even if you pick the incorrect protocol, Darran *thinks* the client will time out after 5 seconds, and the operation will fail. We will still need to close the connection, however. This should be tested heavily, since HTTP and Remoting differ in which side of the connection sends the first data - so get the wrong combo and both sides end up waiting.
3) The Factory.create(etc) method requires a String for protocol, and there is no clear list of values that I've found so far. Darran says: remote, http-remoting and https-remoting. Testing will be required to verify this list
With these 3 things in mind, it seems the biggest question is how to discover the proper protocol from the user's configuration, and, how to display this in the UI. Currently, the management port is grouped in with the ports, and it would not truly make sense to put a different setting there. However, if we move this out, where would it live? It's own section, alone? That also seems difficult to agree to.
> Investigate how to handle Wildfly port multiplexing
> ----------------------------------------------------
>
> Key: JBIDE-15313
> URL: https://issues.jboss.org/browse/JBIDE-15313
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: server
> Affects Versions: 4.1.0.Final
> Reporter: Rob Stryker
> Assignee: Rob Stryker
> Fix For: 4.2.0.Alpha1
>
>
> While JBIDE-14979 and JBIDE-14402 assist in getting wildfly to work out-of-the-box, it does not assist in the possibility of turning multi-plexing on and off. This jira may include additions to UI and API, though it may NOT require both. It remains to be seen.
> This jira will investigate what's necessary and what may need to change.
--
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, 4 months
[JBoss JIRA] (JBIDE-15622) Automatically open/send report when log has error
by Daniel Azarov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15622?page=com.atlassian.jira.plugi... ]
Daniel Azarov updated JBIDE-15622:
----------------------------------
Description:
Step 1:
!ReportError1.png!
Step 2:
!ReportBugStep2.png!
Step 3:
!ReportBugStep3.png!
*Where to:*
1. Error Dialog (Steps 1,2,3) – when problem occurs Error Dialog appears and provides opportunity to report a bug
2. Error Log View (Steps 2,3) (Tool-bar, Menu, Context menu) – report problem for selected stack-trace
3. Help->Report Problem Dialog (Steps 2,3) – report problem which may be not related with any exceptions
1. We should filter this dialog appearance (by Severity, by Existence, by Time), offer automatic send report?
1. and 2. should create issues in “special” project (see Preconditions). 3. may create issues directly to project Tools (JBoss Tools)?
*Feature list:*
1. Log in/Anonymous bug reporting (If the user has login to JIRA he can report issues with it. Or he can do it anonymously)
2. Check Exception Stack-trace for duplicate
3. Report should contain all needed (useful) information about user's environment (JDK/JRE version, eclipse version, OS version, configuration, etc)
4. As much as possible fields should be filled up automatically (project, issue type, priority, component/s, affects version/s, environment) may be some of them should be filled up later by Administrator
5. User should be able to see all the data he is going to send
6. Show communication errors
7. Return link to created JIRA
8. Inform user about the general/common process of bug reporting (see Work-flow)
9. Option to attach log file
10. Option to attach screen-shot
*Preconditions:*
1. We need to create “special” project in JIRA to primary report issue to with anonymous (or dedicated) user.
2. We need person as Administrator (QE-?) to periodically verifying issue from “special” project.
*Work-flow:*
1. User decides/agrees to report the problem (see list Where to)
2. Report Problem dialog appears, user fills up the form
2. Dialog checks for existing exception stack-traces (when stack-trace available) or by key-words from field summary.
3. If validation passes dialog creates issue in “special” project of JIRA (see Preconditions)
4. User gets link to created issue and short description of what will happen next. (features 7. 8.)
5. Administrator should periodically check “special” project and verify all issues. Administrator may reject issue or correct (versions, components etc, if needed) and move to project Tools (JBoss Tools).
*Primary Description:*
JBT should set up an ILogListener on the Eclipse log and send an error report whenever something is logged as error.
As it's probably not possible to send the error report without asking users, it should show the "Report problem" page.
NetBeans does that and has reported an actual quality benefit.
was:
*Where to:*
1. Error Dialog – when problem occurs Error Dialog appears and provides opportunity to report a bug
2. Error Log View (Tool-bar, Menu, Context menu) – report problem for selected stack-trace
3. Help->Report Problem Dialog – report problem which may be not related with any exceptions
1. and 2. should create issues in “special” project (see Preconditions). 3. may create issues directly to project Tools (JBoss Tools)?
*Feature list:*
1. Log in/Anonymous bug reporting (If the user has login to JIRA he can report issues with it. Or he can do it anonymously)
2. Check Exception Stack-trace for duplicate
3. Report should contain all needed (useful) information about user's environment (JDK/JRE version, eclipse version, OS version, configuration, etc)
4. As much as possible fields should be filled up automatically (project, issue type, priority, component/s, affects version/s, environment) may be some of them should be filled up later by Administrator
5. User should be able to see all the data he is going to send
6. Show communication errors
7. Return link to created JIRA
8. Inform user about the general/common process of bug reporting (see Work-flow)
9. Option to attach log file
10. Option to attach screen-shot
*Preconditions:*
1. We need to create “special” project in JIRA to primary report issue to with anonymous (or dedicated) user.
2. We need person as Administrator (QE-?) to periodically verifying issue from “special” project.
*Work-flow:*
1. User decides/agrees to report the problem (see list Where to)
2. Report Problem dialog appears, user fills up the form
2. Dialog checks for existing exception stack-traces (when stack-trace available) or by key-words from field summary.
3. If validation passes dialog creates issue in “special” project of JIRA (see Preconditions)
4. User gets link to created issue and short description of what will happen next. (features 7. 8.)
5. Administrator should periodically check “special” project and verify all issues. Administrator may reject issue or correct (versions, components etc, if needed) and move to project Tools (JBoss Tools).
*Primary Description:*
JBT should set up an ILogListener on the Eclipse log and send an error report whenever something is logged as error.
As it's probably not possible to send the error report without asking users, it should show the "Report problem" page.
NetBeans does that and has reported an actual quality benefit.
> Automatically open/send report when log has error
> -------------------------------------------------
>
> Key: JBIDE-15622
> URL: https://issues.jboss.org/browse/JBIDE-15622
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: common/jst/core
> Affects Versions: 4.1.1.Alpha1
> Reporter: Mickael Istria
> Attachments: ReportBugStep2.bmml, ReportBugStep2.bmml, ReportBugStep2.png, ReportBugStep3.bmml, ReportBugStep3.bmml, ReportBugStep3.bmml, ReportBugStep3.png, ReportError1.bmml, ReportError1.bmml, ReportError1.png
>
>
> Step 1:
> !ReportError1.png!
> Step 2:
> !ReportBugStep2.png!
> Step 3:
> !ReportBugStep3.png!
> *Where to:*
> 1. Error Dialog (Steps 1,2,3) – when problem occurs Error Dialog appears and provides opportunity to report a bug
> 2. Error Log View (Steps 2,3) (Tool-bar, Menu, Context menu) – report problem for selected stack-trace
> 3. Help->Report Problem Dialog (Steps 2,3) – report problem which may be not related with any exceptions
> 1. We should filter this dialog appearance (by Severity, by Existence, by Time), offer automatic send report?
> 1. and 2. should create issues in “special” project (see Preconditions). 3. may create issues directly to project Tools (JBoss Tools)?
> *Feature list:*
> 1. Log in/Anonymous bug reporting (If the user has login to JIRA he can report issues with it. Or he can do it anonymously)
> 2. Check Exception Stack-trace for duplicate
> 3. Report should contain all needed (useful) information about user's environment (JDK/JRE version, eclipse version, OS version, configuration, etc)
> 4. As much as possible fields should be filled up automatically (project, issue type, priority, component/s, affects version/s, environment) may be some of them should be filled up later by Administrator
> 5. User should be able to see all the data he is going to send
> 6. Show communication errors
> 7. Return link to created JIRA
> 8. Inform user about the general/common process of bug reporting (see Work-flow)
> 9. Option to attach log file
> 10. Option to attach screen-shot
> *Preconditions:*
> 1. We need to create “special” project in JIRA to primary report issue to with anonymous (or dedicated) user.
> 2. We need person as Administrator (QE-?) to periodically verifying issue from “special” project.
> *Work-flow:*
> 1. User decides/agrees to report the problem (see list Where to)
> 2. Report Problem dialog appears, user fills up the form
> 2. Dialog checks for existing exception stack-traces (when stack-trace available) or by key-words from field summary.
> 3. If validation passes dialog creates issue in “special” project of JIRA (see Preconditions)
> 4. User gets link to created issue and short description of what will happen next. (features 7. 8.)
> 5. Administrator should periodically check “special” project and verify all issues. Administrator may reject issue or correct (versions, components etc, if needed) and move to project Tools (JBoss Tools).
> *Primary Description:*
> JBT should set up an ILogListener on the Eclipse log and send an error report whenever something is logged as error.
> As it's probably not possible to send the error report without asking users, it should show the "Report problem" page.
> NetBeans does that and has reported an actual quality benefit.
--
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, 4 months
[JBoss JIRA] (JBIDE-16088) Compilation error when building WebServices against Luna TP
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16088?page=com.atlassian.jira.plugi... ]
Denis Golovin edited comment on JBIDE-16088 at 11/26/13 12:28 PM:
------------------------------------------------------------------
There is an issue https://bugs.eclipse.org/bugs/show_bug.cgi?id=413450 it says
{quote}In Luna the Equinox framework no longer publishes the PlatformAdmin service. This causes the method org.eclipse.core.runtime.Platform.getPlatformAdmin() to return null unless the compatibility fragment *org.eclipse.osgi.compatibility.state* is installed.{quote}
was (Author: dgolovin):
There is an issue https://bugs.eclipse.org/bugs/show_bug.cgi?id=413450 it says
{quote}In Luna the Equinox framework no longer publishes the PlatformAdmin service. This causes the method org.eclipse.core.runtime.Platform.getPlatformAdmin() to return null unless the compatibility fragment org.eclipse.osgi.compatibility.state is installed.{quote}
> Compilation error when building WebServices against Luna TP
> -----------------------------------------------------------
>
> Key: JBIDE-16088
> URL: https://issues.jboss.org/browse/JBIDE-16088
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: target-platform, webservices
> Reporter: Xavier Coulon
> Assignee: Brian Fitzpatrick
> Fix For: 4.2.0.Alpha1
>
>
> I have the following dependency resolution problem when building the Web Services component against the Luna TP:
> {code}
> [INFO] Resolving dependencies of MavenProject: org.jboss.tools.ws.plugins:org.jboss.tools.ws.creation.core:1.6.0-SNAPSHOT @ /Users/xcoulon/code/jbosstools/jbosstools-webservices/plugins/org.jboss.tools.ws.creation.core/pom.xml
> [INFO] Cannot complete the request. Generating details.
> [INFO] Cannot complete the request. Generating details.
> [INFO] {osgi.ws=cocoa, osgi.os=macosx, osgi.arch=x86, org.eclipse.update.install.features=true}
> [ERROR] Cannot resolve project dependencies:
> [ERROR] Software being installed: org.jboss.tools.ws.creation.core 1.6.0.qualifier
> [ERROR] Missing requirement: org.jboss.tools.ws.creation.core 1.6.0.qualifier requires 'bundle org.apache.ant [1.8.2,1.9.0)' but it could not be found
> [ERROR]
> [ERROR] Internal error: java.lang.RuntimeException: No solution found because the problem is unsatisfiable.: [Unable to satisfy dependency from org.jboss.tools.ws.creation.core 1.6.0.qualifier to bundle org.apache.ant [1.8.2,1.9.0).; No solution found because the problem is unsatisfiable.] -> [Help 1]
> org.apache.maven.InternalErrorException: Internal error: java.lang.RuntimeException: No solution found because the problem is unsatisfiable.: [Unable to satisfy dependency from org.jboss.tools.ws.creation.core 1.6.0.qualifier to bundle org.apache.ant [1.8.2,1.9.0).; No solution found because the problem is unsatisfiable.]
> {code}
--
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, 4 months
[JBoss JIRA] (JBIDE-16088) Compilation error when building WebServices against Luna TP
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16088?page=com.atlassian.jira.plugi... ]
Denis Golovin commented on JBIDE-16088:
---------------------------------------
There is an issue https://bugs.eclipse.org/bugs/show_bug.cgi?id=413450 it says
{quote}In Luna the Equinox framework no longer publishes the PlatformAdmin service. This causes the method org.eclipse.core.runtime.Platform.getPlatformAdmin() to return null unless the compatibility fragment org.eclipse.osgi.compatibility.state is installed.{quote}
> Compilation error when building WebServices against Luna TP
> -----------------------------------------------------------
>
> Key: JBIDE-16088
> URL: https://issues.jboss.org/browse/JBIDE-16088
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: target-platform, webservices
> Reporter: Xavier Coulon
> Assignee: Brian Fitzpatrick
> Fix For: 4.2.0.Alpha1
>
>
> I have the following dependency resolution problem when building the Web Services component against the Luna TP:
> {code}
> [INFO] Resolving dependencies of MavenProject: org.jboss.tools.ws.plugins:org.jboss.tools.ws.creation.core:1.6.0-SNAPSHOT @ /Users/xcoulon/code/jbosstools/jbosstools-webservices/plugins/org.jboss.tools.ws.creation.core/pom.xml
> [INFO] Cannot complete the request. Generating details.
> [INFO] Cannot complete the request. Generating details.
> [INFO] {osgi.ws=cocoa, osgi.os=macosx, osgi.arch=x86, org.eclipse.update.install.features=true}
> [ERROR] Cannot resolve project dependencies:
> [ERROR] Software being installed: org.jboss.tools.ws.creation.core 1.6.0.qualifier
> [ERROR] Missing requirement: org.jboss.tools.ws.creation.core 1.6.0.qualifier requires 'bundle org.apache.ant [1.8.2,1.9.0)' but it could not be found
> [ERROR]
> [ERROR] Internal error: java.lang.RuntimeException: No solution found because the problem is unsatisfiable.: [Unable to satisfy dependency from org.jboss.tools.ws.creation.core 1.6.0.qualifier to bundle org.apache.ant [1.8.2,1.9.0).; No solution found because the problem is unsatisfiable.] -> [Help 1]
> org.apache.maven.InternalErrorException: Internal error: java.lang.RuntimeException: No solution found because the problem is unsatisfiable.: [Unable to satisfy dependency from org.jboss.tools.ws.creation.core 1.6.0.qualifier to bundle org.apache.ant [1.8.2,1.9.0).; No solution found because the problem is unsatisfiable.]
> {code}
--
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, 4 months
[JBoss JIRA] (JBIDE-16032) java.lang.ArrayIndexOutOfBoundsException in Forge Runtime preferences
by Pavol Srna (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16032?page=com.atlassian.jira.plugi... ]
Pavol Srna commented on JBIDE-16032:
------------------------------------
[~koen.aers] yes I'am sure. I tried it again on JBDS:
Version: 7.1.0.CR1
Build id: CR1-v20131124-0717-B560
Build date: 20131124-0717
Obviously something has changed because the line numbers are different. Please see the stacktrace below. But UI behaves the same and I still hit the issue.
{code}
java.lang.ArrayIndexOutOfBoundsException: 0
at org.jboss.tools.forge.ui.preferences.ForgeInstallationsPreferencePage.enableButtons(ForgeInstallationsPreferencePage.java:286)
at org.jboss.tools.forge.ui.preferences.ForgeInstallationsPreferencePage.access$4(ForgeInstallationsPreferencePage.java:275)
at org.jboss.tools.forge.ui.preferences.ForgeInstallationsPreferencePage$4.selectionChanged(ForgeInstallationsPreferencePage.java:177)
at org.eclipse.jface.viewers.Viewer$2.run(Viewer.java:164)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:49)
at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:175)
at org.eclipse.jface.viewers.Viewer.fireSelectionChanged(Viewer.java:162)
at org.eclipse.jface.viewers.StructuredViewer.updateSelection(StructuredViewer.java:2188)
at org.eclipse.jface.viewers.StructuredViewer.handleSelect(StructuredViewer.java:1211)
at org.eclipse.jface.viewers.CheckboxTableViewer.handleSelect(CheckboxTableViewer.java:301)
at org.eclipse.jface.viewers.StructuredViewer$4.widgetSelected(StructuredViewer.java:1241)
at org.eclipse.jface.util.OpenStrategy.fireSelectionEvent(OpenStrategy.java:239)
at org.eclipse.jface.util.OpenStrategy.access$4(OpenStrategy.java:233)
at org.eclipse.jface.util.OpenStrategy$1.handleEvent(OpenStrategy.java:403)
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:3742)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3363)
at org.eclipse.jface.window.Window.runEventLoop(Window.java:826)
at org.eclipse.jface.window.Window.open(Window.java:802)
at org.eclipse.ui.internal.dialogs.WorkbenchPreferenceDialog.open(WorkbenchPreferenceDialog.java:215)
at org.eclipse.ui.internal.OpenPreferencesAction.run(OpenPreferencesAction.java:65)
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:3742)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3363)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1113)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:997)
at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:138)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:610)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:567)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
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:606)
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}
> java.lang.ArrayIndexOutOfBoundsException in Forge Runtime preferences
> ---------------------------------------------------------------------
>
> Key: JBIDE-16032
> URL: https://issues.jboss.org/browse/JBIDE-16032
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: forge
> Reporter: Pavol Srna
> Assignee: Koen Aers
> Labels: respin-a
> Fix For: 4.1.1.CR1
>
> Attachments: forge-preferences.png
>
>
> Stacktrace:
> {code}
> java.lang.ArrayIndexOutOfBoundsException: 0
> at org.jboss.tools.forge.ui.preferences.ForgeInstallationsPreferencePage$6.run(ForgeInstallationsPreferencePage.java:293)
> at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
> at org.jboss.tools.forge.ui.preferences.ForgeInstallationsPreferencePage.performOk(ForgeInstallationsPreferencePage.java:290)
> at org.eclipse.jface.preference.PreferenceDialog$13.run(PreferenceDialog.java:965)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:49)
> at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:175)
> at org.eclipse.jface.preference.PreferenceDialog.okPressed(PreferenceDialog.java:945)
> at org.eclipse.ui.internal.dialogs.FilteredPreferenceDialog.okPressed(FilteredPreferenceDialog.java:448)
> at org.eclipse.ui.internal.dialogs.WorkbenchPreferenceDialog.okPressed(WorkbenchPreferenceDialog.java:171)
> at org.eclipse.jface.preference.PreferenceDialog.buttonPressed(PreferenceDialog.java:233)
> at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:628)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248)
> 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:3742)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3363)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:826)
> at org.eclipse.jface.window.Window.open(Window.java:802)
> at org.eclipse.ui.internal.dialogs.WorkbenchPreferenceDialog.open(WorkbenchPreferenceDialog.java:215)
> at org.eclipse.ui.internal.OpenPreferencesAction.run(OpenPreferencesAction.java:65)
> 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:3742)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3363)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1113)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:997)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:138)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:610)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:567)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> 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:606)
> 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}
--
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, 4 months
[JBoss JIRA] (JBDS-2833) CLONE - Installer fails due to spaces in JDK path on Windows 8
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-2833?page=com.atlassian.jira.plugin.... ]
Denis Golovin commented on JBDS-2833:
-------------------------------------
I don't have privileges ether, I guess because two more CDW fields are still under question.
> CLONE - Installer fails due to spaces in JDK path on Windows 8
> --------------------------------------------------------------
>
> Key: JBDS-2833
> URL: https://issues.jboss.org/browse/JBDS-2833
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: installer, upstream
> Environment: Windows 8, Oracle JRE 1.6 x86_64/x86
> Reporter: Pavol Srna
> Assignee: Denis Golovin
> Priority: Blocker
> Fix For: 8.0.0.Alpha1
>
>
> {code}C:\Users\alena\Downloads>java -jar jbdevstudio-product-universal-7.0.0.Beta2-B26
> 1.jar
> java.io.IOException: Cannot run program "C:\Program": CreateProcess error=2, The
> system cannot find the file specified
> at java.lang.ProcessBuilder.start(Unknown Source)
> at java.lang.Runtime.exec(Unknown Source)
> at java.lang.Runtime.exec(Unknown Source)
> at java.lang.Runtime.exec(Unknown Source)
> at com.izforge.izpack.util.LibraryRemover.initJavaExec(Unknown Source)
> at com.izforge.izpack.util.LibraryRemover.<init>(Unknown Source)
> at com.izforge.izpack.util.LibraryRemover.invoke(Unknown Source)
> at com.izforge.izpack.util.Librarian.cleanUp(Unknown Source)
> at com.izforge.izpack.util.Housekeeper.shutDown(Unknown Source)
> at com.izforge.izpack.installer.InstallerFrame.exit(InstallerFrame.java:
> 1161)
> at com.izforge.izpack.installer.InstallerFrame$NavigationHandler.actionP
> erformed(InstallerFrame.java:1562)
> at javax.swing.AbstractButton.fireActionPerformed(Unknown Source)
> at javax.swing.AbstractButton$Handler.actionPerformed(Unknown Source)
> at javax.swing.DefaultButtonModel.fireActionPerformed(Unknown Source)
> at javax.swing.DefaultButtonModel.setPressed(Unknown Source)
> at javax.swing.plaf.basic.BasicButtonListener.mouseReleased(Unknown Sour
> ce)
> at java.awt.Component.processMouseEvent(Unknown Source)
> at javax.swing.JComponent.processMouseEvent(Unknown Source)
> at java.awt.Component.processEvent(Unknown Source)
> at java.awt.Container.processEvent(Unknown Source)
> at java.awt.Component.dispatchEventImpl(Unknown Source)
> at java.awt.Container.dispatchEventImpl(Unknown Source)
> at java.awt.Component.dispatchEvent(Unknown Source)
> at java.awt.LightweightDispatcher.retargetMouseEvent(Unknown Source)
> at java.awt.LightweightDispatcher.processMouseEvent(Unknown Source)
> at java.awt.LightweightDispatcher.dispatchEvent(Unknown Source)
> at java.awt.Container.dispatchEventImpl(Unknown Source)
> at java.awt.Window.dispatchEventImpl(Unknown Source)
> at java.awt.Component.dispatchEvent(Unknown Source)
> at java.awt.EventQueue.dispatchEventImpl(Unknown Source)
> at java.awt.EventQueue.access$400(Unknown Source)
> at java.awt.EventQueue$2.run(Unknown Source)
> at java.awt.EventQueue$2.run(Unknown Source)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.security.AccessControlContext$1.doIntersectionPrivilege(Unknown
> Source)
> at java.security.AccessControlContext$1.doIntersectionPrivilege(Unknown
> Source)
> at java.awt.EventQueue$3.run(Unknown Source)
> at java.awt.EventQueue$3.run(Unknown Source)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.security.AccessControlContext$1.doIntersectionPrivilege(Unknown
> Source)
> at java.awt.EventQueue.dispatchEvent(Unknown Source)
> at java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown Source)
> at java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source)
> at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
> at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
> at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
> at java.awt.EventDispatchThread.run(Unknown Source)
> Caused by: java.io.IOException: CreateProcess error=2, The system cannot find th
> e file specified
> at java.lang.ProcessImpl.create(Native Method)
> at java.lang.ProcessImpl.<init>(Unknown Source)
> at java.lang.ProcessImpl.start(Unknown Source)
> ... 47 more{code}
--
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, 4 months
[JBoss JIRA] (JBDS-2833) CLONE - Installer fails due to spaces in JDK path on Windows 8
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-2833?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-2833:
--------------------------------
CDW devel_ack: + (was: ?)
Status: New (was: New)
> CLONE - Installer fails due to spaces in JDK path on Windows 8
> --------------------------------------------------------------
>
> Key: JBDS-2833
> URL: https://issues.jboss.org/browse/JBDS-2833
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: installer, upstream
> Environment: Windows 8, Oracle JRE 1.6 x86_64/x86
> Reporter: Pavol Srna
> Assignee: Denis Golovin
> Priority: Blocker
> Fix For: 8.0.0.Alpha1
>
>
> {code}C:\Users\alena\Downloads>java -jar jbdevstudio-product-universal-7.0.0.Beta2-B26
> 1.jar
> java.io.IOException: Cannot run program "C:\Program": CreateProcess error=2, The
> system cannot find the file specified
> at java.lang.ProcessBuilder.start(Unknown Source)
> at java.lang.Runtime.exec(Unknown Source)
> at java.lang.Runtime.exec(Unknown Source)
> at java.lang.Runtime.exec(Unknown Source)
> at com.izforge.izpack.util.LibraryRemover.initJavaExec(Unknown Source)
> at com.izforge.izpack.util.LibraryRemover.<init>(Unknown Source)
> at com.izforge.izpack.util.LibraryRemover.invoke(Unknown Source)
> at com.izforge.izpack.util.Librarian.cleanUp(Unknown Source)
> at com.izforge.izpack.util.Housekeeper.shutDown(Unknown Source)
> at com.izforge.izpack.installer.InstallerFrame.exit(InstallerFrame.java:
> 1161)
> at com.izforge.izpack.installer.InstallerFrame$NavigationHandler.actionP
> erformed(InstallerFrame.java:1562)
> at javax.swing.AbstractButton.fireActionPerformed(Unknown Source)
> at javax.swing.AbstractButton$Handler.actionPerformed(Unknown Source)
> at javax.swing.DefaultButtonModel.fireActionPerformed(Unknown Source)
> at javax.swing.DefaultButtonModel.setPressed(Unknown Source)
> at javax.swing.plaf.basic.BasicButtonListener.mouseReleased(Unknown Sour
> ce)
> at java.awt.Component.processMouseEvent(Unknown Source)
> at javax.swing.JComponent.processMouseEvent(Unknown Source)
> at java.awt.Component.processEvent(Unknown Source)
> at java.awt.Container.processEvent(Unknown Source)
> at java.awt.Component.dispatchEventImpl(Unknown Source)
> at java.awt.Container.dispatchEventImpl(Unknown Source)
> at java.awt.Component.dispatchEvent(Unknown Source)
> at java.awt.LightweightDispatcher.retargetMouseEvent(Unknown Source)
> at java.awt.LightweightDispatcher.processMouseEvent(Unknown Source)
> at java.awt.LightweightDispatcher.dispatchEvent(Unknown Source)
> at java.awt.Container.dispatchEventImpl(Unknown Source)
> at java.awt.Window.dispatchEventImpl(Unknown Source)
> at java.awt.Component.dispatchEvent(Unknown Source)
> at java.awt.EventQueue.dispatchEventImpl(Unknown Source)
> at java.awt.EventQueue.access$400(Unknown Source)
> at java.awt.EventQueue$2.run(Unknown Source)
> at java.awt.EventQueue$2.run(Unknown Source)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.security.AccessControlContext$1.doIntersectionPrivilege(Unknown
> Source)
> at java.security.AccessControlContext$1.doIntersectionPrivilege(Unknown
> Source)
> at java.awt.EventQueue$3.run(Unknown Source)
> at java.awt.EventQueue$3.run(Unknown Source)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.security.AccessControlContext$1.doIntersectionPrivilege(Unknown
> Source)
> at java.awt.EventQueue.dispatchEvent(Unknown Source)
> at java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown Source)
> at java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source)
> at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
> at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
> at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
> at java.awt.EventDispatchThread.run(Unknown Source)
> Caused by: java.io.IOException: CreateProcess error=2, The system cannot find th
> e file specified
> at java.lang.ProcessImpl.create(Native Method)
> at java.lang.ProcessImpl.<init>(Unknown Source)
> at java.lang.ProcessImpl.start(Unknown Source)
> ... 47 more{code}
--
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, 4 months
[JBoss JIRA] (JBIDE-16101) Broken layout of feature description with "Technology Preview" text on Fedora
by Vlado Pakan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16101?page=com.atlassian.jira.plugi... ]
Vlado Pakan commented on JBIDE-16101:
-------------------------------------
To build it locally it's to much work for me right now I do not have time for it.
But I suppose it will be still broken because your PR didn't fix anything with layout just displayed text. And it looks similar to what I have with "Technology Preview" text. Looks like problem with text with two words. Even if we will use just one word we should fix this layout problem to be able to display two or more words correctly in future.
And it should works exactly on your PC where it's broken. It's already working on Windows and MacOSX but should be fixed on Fedora/Linux.
> Broken layout of feature description with "Technology Preview" text on Fedora
> -----------------------------------------------------------------------------
>
> Key: JBIDE-16101
> URL: https://issues.jboss.org/browse/JBIDE-16101
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.1.1.CR1
> Environment: Fedora 18 64bit KDE, JBDS7.1.0.CR1 CR1-v20131124-0717-B560
> -Djboss.discovery.directory.url=http://www.qa.jboss.com/binaries/RHDS/discovery/development/7.1.0.CR1a/devstudio-directory.xml
> -Djboss.discovery.site.url=http://www.qa.jboss.com/binaries/RHDS/discovery/development/7.1.0.CR1a/
> Reporter: Vlado Pakan
> Assignee: Nick Boldt
> Priority: Minor
> Fix For: 4.2.x
>
> Attachments: jbide16101-not-sure-if-better.png, technologypreview.png
>
>
> Instead of link with text "Technology Preview" only link with text "Technology" is displayed within Central as patr of JBoss Hybrid Mobile Mobile Tools + CordovaSim item in JBoss Central.
> !technologypreview.png!
> It's displayed correctly on OSX.
--
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, 4 months
[JBoss JIRA] (JBIDE-16101) Broken layout of feature description with "Technology Preview" text on Fedora
by Mustafa Musaji (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16101?page=com.atlassian.jira.plugi... ]
Mustafa Musaji commented on JBIDE-16101:
----------------------------------------
[~nickboldt] I'm fine with "Preview" or "Tech Preview". I think it reads better as "Tech Preview" but as long as the tool-tip is in place then it's fine.
> Broken layout of feature description with "Technology Preview" text on Fedora
> -----------------------------------------------------------------------------
>
> Key: JBIDE-16101
> URL: https://issues.jboss.org/browse/JBIDE-16101
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.1.1.CR1
> Environment: Fedora 18 64bit KDE, JBDS7.1.0.CR1 CR1-v20131124-0717-B560
> -Djboss.discovery.directory.url=http://www.qa.jboss.com/binaries/RHDS/discovery/development/7.1.0.CR1a/devstudio-directory.xml
> -Djboss.discovery.site.url=http://www.qa.jboss.com/binaries/RHDS/discovery/development/7.1.0.CR1a/
> Reporter: Vlado Pakan
> Assignee: Nick Boldt
> Priority: Minor
> Fix For: 4.2.x
>
> Attachments: jbide16101-not-sure-if-better.png, technologypreview.png
>
>
> Instead of link with text "Technology Preview" only link with text "Technology" is displayed within Central as patr of JBoss Hybrid Mobile Mobile Tools + CordovaSim item in JBoss Central.
> !technologypreview.png!
> It's displayed correctly on OSX.
--
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, 4 months