[JBoss JIRA] (JBIDE-16137) webservices component build hangs during tests on MacOSX 10.7
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16137?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-16137:
----------------------------------------
Anything in the .log file? (target/work/data/.metadata/.log)
> webservices component build hangs during tests on MacOSX 10.7
> -------------------------------------------------------------
>
> Key: JBIDE-16137
> URL: https://issues.jboss.org/browse/JBIDE-16137
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, webservices
> Affects Versions: 4.2.0.Alpha1
> Environment: Luna 4.4 M3 TP
> Reporter: Xavier Coulon
>
> when reaching the tests on org.jboss.tools.ws.creation.core.tests, a workbench window appears but nothing is drawn and the build hangs with the following content in the console:
> {code}
> [INFO] Command line:
> /bin/sh -c cd /Users/xcoulon/code/jbosstools/jbosstools-webservices/tests/org.jboss.tools.ws.creation.core.test && /Library/Java/JavaVirtualMachines/jdk1.7.0_12.jdk/Contents/Home/jre/bin/java -Dosgi.noShutdown=false -Dosgi.os=macosx -Dosgi.ws=cocoa -Dosgi.arch=x86_64 '-javaagent:/Users/xcoulon/.m2/repository/org/jacoco/org.jacoco.agent/0.6.1.201212231917/org.jacoco.agent-0.6.1.201212231917-runtime.jar=destfile=/Users/xcoulon/code/jbosstools/jbosstools-webservices/target/jacoco.exec,append=true,includes=org.jboss.tools.ws.creation.core*' -Xms512m -Xmx1024m -XX:PermSize=256m -XX:MaxPermSize=256m -XstartOnFirstThread '-Djbosstools.test.jre.6=${jbosstools.test.jre.6}' '-Djbosstools.test.jre.5=${jbosstools.test.jre.5}' -Djbosstools.test.jboss.home.4.2=/Users/xcoulon/code/jbosstools/jbosstools-webservices/tests/org.jboss.tools.ws.creation.core.test/target/requirements/jboss-4.2.3.GA -Dusage_reporting_enabled=false -Dorg.jboss.tools.tests.skipPrivateRequirements=true -Dorg.eclipse.ui.testsDisableWorkbenchAutoSave=true -Dosgi.clean=true -jar /Users/xcoulon/.m2/repository/p2/osgi/bundle/org.eclipse.equinox.launcher/1.3.0.v20130327-1440/org.eclipse.equinox.launcher-1.3.0.v20130327-1440.jar -data /Users/xcoulon/code/jbosstools/jbosstools-webservices/tests/org.jboss.tools.ws.creation.core.test/target/work/data -install /Users/xcoulon/code/jbosstools/jbosstools-webservices/tests/org.jboss.tools.ws.creation.core.test/target/work -configuration /Users/xcoulon/code/jbosstools/jbosstools-webservices/tests/org.jboss.tools.ws.creation.core.test/target/work/configuration -application org.eclipse.tycho.surefire.osgibooter.uitest -testproperties /Users/xcoulon/code/jbosstools/jbosstools-webservices/tests/org.jboss.tools.ws.creation.core.test/target/surefire.properties
> -------------------------------------------------------
> T E S T S
> -------------------------------------------------------
> Running org.jboss.tools.ws.creation.core.test.JBossWSCreationCoreTestSuite
> {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-16137) webservices component build hangs during tests on MacOSX 10.7
by Xavier Coulon (JIRA)
Xavier Coulon created JBIDE-16137:
-------------------------------------
Summary: webservices component build hangs during tests on MacOSX 10.7
Key: JBIDE-16137
URL: https://issues.jboss.org/browse/JBIDE-16137
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: build, webservices
Affects Versions: 4.2.0.Alpha1
Environment: Luna 4.4 M3 TP
Reporter: Xavier Coulon
when reaching the tests on org.jboss.tools.ws.creation.core.tests, a workbench window appears but nothing is drawn and the build hangs with the following content in the console:
{code}
[INFO] Command line:
/bin/sh -c cd /Users/xcoulon/code/jbosstools/jbosstools-webservices/tests/org.jboss.tools.ws.creation.core.test && /Library/Java/JavaVirtualMachines/jdk1.7.0_12.jdk/Contents/Home/jre/bin/java -Dosgi.noShutdown=false -Dosgi.os=macosx -Dosgi.ws=cocoa -Dosgi.arch=x86_64 '-javaagent:/Users/xcoulon/.m2/repository/org/jacoco/org.jacoco.agent/0.6.1.201212231917/org.jacoco.agent-0.6.1.201212231917-runtime.jar=destfile=/Users/xcoulon/code/jbosstools/jbosstools-webservices/target/jacoco.exec,append=true,includes=org.jboss.tools.ws.creation.core*' -Xms512m -Xmx1024m -XX:PermSize=256m -XX:MaxPermSize=256m -XstartOnFirstThread '-Djbosstools.test.jre.6=${jbosstools.test.jre.6}' '-Djbosstools.test.jre.5=${jbosstools.test.jre.5}' -Djbosstools.test.jboss.home.4.2=/Users/xcoulon/code/jbosstools/jbosstools-webservices/tests/org.jboss.tools.ws.creation.core.test/target/requirements/jboss-4.2.3.GA -Dusage_reporting_enabled=false -Dorg.jboss.tools.tests.skipPrivateRequirements=true -Dorg.eclipse.ui.testsDisableWorkbenchAutoSave=true -Dosgi.clean=true -jar /Users/xcoulon/.m2/repository/p2/osgi/bundle/org.eclipse.equinox.launcher/1.3.0.v20130327-1440/org.eclipse.equinox.launcher-1.3.0.v20130327-1440.jar -data /Users/xcoulon/code/jbosstools/jbosstools-webservices/tests/org.jboss.tools.ws.creation.core.test/target/work/data -install /Users/xcoulon/code/jbosstools/jbosstools-webservices/tests/org.jboss.tools.ws.creation.core.test/target/work -configuration /Users/xcoulon/code/jbosstools/jbosstools-webservices/tests/org.jboss.tools.ws.creation.core.test/target/work/configuration -application org.eclipse.tycho.surefire.osgibooter.uitest -testproperties /Users/xcoulon/code/jbosstools/jbosstools-webservices/tests/org.jboss.tools.ws.creation.core.test/target/surefire.properties
-------------------------------------------------------
T E S T S
-------------------------------------------------------
Running org.jboss.tools.ws.creation.core.test.JBossWSCreationCoreTestSuite
{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:
------------------------------------
Unfortunately no, I see the same issue in JBT too.
> 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] (JBIDE-2720) Need 64-bit windows support
by Maria Beltrán (JIRA)
[ https://issues.jboss.org/browse/JBIDE-2720?page=com.atlassian.jira.plugin... ]
Maria Beltrán commented on JBIDE-2720:
--------------------------------------
Hi Nick, I go to upgrate them and I will back to you.
Thanks for your help
Saludos desde Barcelona
Mar
> 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: Konstantin Marmalyukov
> Fix For: 4.2.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, c-runtime-error.png, mozconfig1, mozconfig2, vpe-win-jdk64.png
>
>
> If you use a 64-bit JVM, the XULRunner parts of JBoss Tools does not load.
> We should look into providing a xulrunner for Windows 64-bit.
> *Update:*
> In JBoss Tools 4.1.0 and JBoss Developer Studio 7.0.0 XULRunner for 64-bit Windows is provided via experimental update site: http://download.jboss.org/jbosstools/updates/integration/kepler/core/xulr...
> {color:red}*Known problems:*{color}
> * XULRunner for 64-bit Windows is incompatible with Intel OpenCL SDK
> *If you get [R6034 error|https://issues.jboss.org/browse/JBIDE-2720?focusedCommentId=1277169...] you may:*
> * Try to uninstall Intel OpenCL SDK
> * *OR* Disable XULRunner by adding the option {{-Dorg.jboss.tools.vpe.loadxulrunner=false}} to the {{eclipse.ini}} (or {{jbdevstudio.ini}} if you use JBoss Developer Studio)
> If you do not have Intel OpenCL SDK installed but still getting the R6034 error, we will very appreciate if you run Process Explorer as described in [this comment|https://issues.jboss.org/browse/JBIDE-2720?focusedCommentId=12772...] and help us to find conflicting library.
--
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 Koen Aers (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16032?page=com.atlassian.jira.plugi... ]
Koen Aers commented on JBIDE-16032:
-----------------------------------
So maybe this change was included in JBT 4.1.1.CR1a but not propagated to JBDS?
> 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] (JBIDE-15622) Automatically open/send report when log has error
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15622?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-15622:
----------------------------------------
Here are the links to the NetBeans modules taking care of this:
* http://hg.netbeans.org/main/file/75d87146ecd3/bugzilla
* http://hg.netbeans.org/main/file/75d87146ecd3/bugzilla.exceptionreporter
Some UI suggestions:
* About credentials:
** page needs a link to create a Jira account if user doesn't have one.
** page should be the last page (to avoid getting back if credentials aren't correct, which happens often with passwords)
* I don't see the value of the "Source view" for the issue. Why not sticking just to the form?
> 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.bmml, ReportBugStep3.png, ReportBugStep3SourceView.bmml, ReportBugStep3SourceView.bmml, ReportBugStep3SourceView.png, ReportError1.bmml, ReportError1.bmml, ReportError1.png
>
>
> Step 1:
> !ReportError1.png!
> Step 2:
> !ReportBugStep2.png!
> Step 3:
> !ReportBugStep3.png!
> !ReportBugStep3SourceView.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 (local in log file and remote in JIRA), by Time (not often then one time in a minute, in case of crash where could be a lot of exceptions in short period of 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-15934) Run on Android Device does not work on OS X
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15934?page=com.atlassian.jira.plugi... ]
Martin Malina updated JBIDE-15934:
----------------------------------
Fix Version/s: 4.1.2
(was: 4.1.1.CR1)
> Run on Android Device does not work on OS X
> -------------------------------------------
>
> Key: JBIDE-15934
> URL: https://issues.jboss.org/browse/JBIDE-15934
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid
> Affects Versions: 4.1.1.Beta1
> Environment: OS X Mavericks
> Latest Android SDK
> JBDS 7.1.0.Beta1
> Nexus 7
> Reporter: Martin Malina
> Assignee: Gorkem Ercan
> Fix For: 4.1.2
>
>
> Following the instructions in JBIDE-15904 I am trying to run an app on an Android Device.
> This fails for me - I get: No developer enabled android device is attached to this computer please attach your device and try again. (Punctuation is missing, btw.)
> When I try to run adb devices, I can see the device is not there. Development mode is enabled on the device and it works for Vlado on Linux.
> I found out that using Run on Android Device somehow breaks the connection with the device - before I run that, "adb devices" shows the device just fine. After I run that, the device is no longer displayed.
> We even tried to deploy the app using adb install and it worked (while the device was still connected)
--
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] (TOOLSDOC-384) Technical Review of 7.0 User Guide
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-384?page=com.atlassian.jira.plug... ]
Michelle Murray updated TOOLSDOC-384:
-------------------------------------
Description:
Conduct a post release technical review of 7.0 User Guide to catch any previously missed technical or copy errors.
* JBoss Central and the JBoss Perspective *[done]*
* JBoss Server Tools *[done]*
* Forge Tools *[done]*
* LiveReload Tools *[done]*
* Mobile Web Tools *[done]*
* BrowserSim
* OpenShift Tools
was:
Conduct a post release technical review of 7.0 User Guide to catch any previously missed technical or copy errors.
* JBoss Central and the JBoss Perspective *[done]*
* JBoss Server Tools *[done]*
* Forge Tools *[done]*
* LiveReload Tools *[done]*
* Mobile Web Tools
* BrowserSim
* OpenShift Tools
> Technical Review of 7.0 User Guide
> ----------------------------------
>
> Key: TOOLSDOC-384
> URL: https://issues.jboss.org/browse/TOOLSDOC-384
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Sub-task
> Security Level: Public(Everyone can see)
> Components: User Guide
> Affects Versions: 4.1.0
> Reporter: Michelle Murray
> Assignee: Michelle Murray
> Fix For: 4.1.0
>
>
> Conduct a post release technical review of 7.0 User Guide to catch any previously missed technical or copy errors.
> * JBoss Central and the JBoss Perspective *[done]*
> * JBoss Server Tools *[done]*
> * Forge Tools *[done]*
> * LiveReload Tools *[done]*
> * Mobile Web Tools *[done]*
> * BrowserSim
> * OpenShift Tools
--
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-11164) Widget disposed too early for part org.jboss.tools.central.editors.JBossCentralEditor
by Andrej Podhradsky (JIRA)
[ https://issues.jboss.org/browse/JBIDE-11164?page=com.atlassian.jira.plugi... ]
Andrej Podhradsky closed JBIDE-11164.
-------------------------------------
Resolution: Done
I would rather set 3.3.2.Final as fixed version but I have no idea how to get out the archived version 3.3.0.Beta3
> Widget disposed too early for part org.jboss.tools.central.editors.JBossCentralEditor
> -------------------------------------------------------------------------------------
>
> Key: JBIDE-11164
> URL: https://issues.jboss.org/browse/JBIDE-11164
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 3.3.0.Beta1
> Environment: jbosstools-3.3_stable_branch.aggregate-Update-2012-02-29_14-32-12-H100.zip,L64
> Reporter: Jiri Peterka
> Assignee: Andrej Podhradsky
> Priority: Minor
>
> !ENTRY org.eclipse.ui.workbench 4 0 2012-03-05 13:27:01.277
> !MESSAGE Widget disposed too early for part org.jboss.tools.central.editors.JBossCentralEditor
> !STACK 0
> java.lang.RuntimeException: Widget disposed too early for part org.jboss.tools.central.editors.JBossCentralEditor
> at org.eclipse.ui.internal.WorkbenchPartReference$1.widgetDisposed(WorkbenchPartReference.java:171)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:123)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1258)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1282)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1263)
> at org.eclipse.swt.widgets.Widget.release(Widget.java:1080)
> at org.eclipse.swt.widgets.Control.release(Control.java:3488)
> at org.eclipse.swt.widgets.Composite.releaseChildren(Composite.java:1294)
> at org.eclipse.swt.widgets.Widget.release(Widget.java:1083)
> at org.eclipse.swt.widgets.Control.release(Control.java:3488)
> at org.eclipse.swt.widgets.Widget.dispose(Widget.java:462)
> at org.eclipse.ui.internal.EditorSashContainer.disposeParent(EditorSashContainer.java:195)
> at org.eclipse.ui.internal.PartSashContainer.dispose(PartSashContainer.java:599)
> at org.eclipse.ui.internal.EditorSashContainer.dispose(EditorSashContainer.java:187)
> at org.eclipse.ui.internal.EditorAreaHelper.dispose(EditorAreaHelper.java:125)
> at org.eclipse.ui.internal.WorkbenchPage.dispose(WorkbenchPage.java:1898)
> at org.eclipse.ui.internal.WorkbenchWindow.closeAllPages(WorkbenchWindow.java:894)
> at org.eclipse.ui.internal.WorkbenchWindow.hardClose(WorkbenchWindow.java:1729)
> at org.eclipse.ui.internal.WorkbenchWindow.busyClose(WorkbenchWindow.java:730)
> at org.eclipse.ui.internal.WorkbenchWindow.access$0(WorkbenchWindow.java:715)
> at org.eclipse.ui.internal.WorkbenchWindow$6.run(WorkbenchWindow.java:867)
> at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
> at org.eclipse.ui.internal.WorkbenchWindow.close(WorkbenchWindow.java:865)
> at org.eclipse.jface.window.WindowManager.close(WindowManager.java:109)
> at org.eclipse.ui.internal.Workbench$18.run(Workbench.java:1114)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.ui.internal.Workbench.busyClose(Workbench.java:1111)
> at org.eclipse.ui.internal.Workbench.access$15(Workbench.java:1040)
> at org.eclipse.ui.internal.Workbench$25.run(Workbench.java:1284)
> at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
> at org.eclipse.ui.internal.Workbench.close(Workbench.java:1282)
> at org.eclipse.ui.internal.Workbench.close(Workbench.java:1254)
> at org.eclipse.ui.internal.testing.WorkbenchTestable$2.run(WorkbenchTestable.java:124)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3563)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3212)
> at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2701)
> at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2665)
> at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2499)
> at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:679)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:668)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:123)
> at org.eclipse.swtbot.eclipse.core.UITestApplication.start(UITestApplication.java:54)
> 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:344)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1410)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1386)
--
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-11164) Widget disposed too early for part org.jboss.tools.central.editors.JBossCentralEditor
by Andrej Podhradsky (JIRA)
[ https://issues.jboss.org/browse/JBIDE-11164?page=com.atlassian.jira.plugi... ]
Andrej Podhradsky updated JBIDE-11164:
--------------------------------------
Fix Version/s: (was: 3.3.2.Final)
> Widget disposed too early for part org.jboss.tools.central.editors.JBossCentralEditor
> -------------------------------------------------------------------------------------
>
> Key: JBIDE-11164
> URL: https://issues.jboss.org/browse/JBIDE-11164
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 3.3.0.Beta1
> Environment: jbosstools-3.3_stable_branch.aggregate-Update-2012-02-29_14-32-12-H100.zip,L64
> Reporter: Jiri Peterka
> Assignee: Andrej Podhradsky
> Priority: Minor
> Fix For: 3.3.0.Beta3
>
>
> !ENTRY org.eclipse.ui.workbench 4 0 2012-03-05 13:27:01.277
> !MESSAGE Widget disposed too early for part org.jboss.tools.central.editors.JBossCentralEditor
> !STACK 0
> java.lang.RuntimeException: Widget disposed too early for part org.jboss.tools.central.editors.JBossCentralEditor
> at org.eclipse.ui.internal.WorkbenchPartReference$1.widgetDisposed(WorkbenchPartReference.java:171)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:123)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1258)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1282)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1263)
> at org.eclipse.swt.widgets.Widget.release(Widget.java:1080)
> at org.eclipse.swt.widgets.Control.release(Control.java:3488)
> at org.eclipse.swt.widgets.Composite.releaseChildren(Composite.java:1294)
> at org.eclipse.swt.widgets.Widget.release(Widget.java:1083)
> at org.eclipse.swt.widgets.Control.release(Control.java:3488)
> at org.eclipse.swt.widgets.Widget.dispose(Widget.java:462)
> at org.eclipse.ui.internal.EditorSashContainer.disposeParent(EditorSashContainer.java:195)
> at org.eclipse.ui.internal.PartSashContainer.dispose(PartSashContainer.java:599)
> at org.eclipse.ui.internal.EditorSashContainer.dispose(EditorSashContainer.java:187)
> at org.eclipse.ui.internal.EditorAreaHelper.dispose(EditorAreaHelper.java:125)
> at org.eclipse.ui.internal.WorkbenchPage.dispose(WorkbenchPage.java:1898)
> at org.eclipse.ui.internal.WorkbenchWindow.closeAllPages(WorkbenchWindow.java:894)
> at org.eclipse.ui.internal.WorkbenchWindow.hardClose(WorkbenchWindow.java:1729)
> at org.eclipse.ui.internal.WorkbenchWindow.busyClose(WorkbenchWindow.java:730)
> at org.eclipse.ui.internal.WorkbenchWindow.access$0(WorkbenchWindow.java:715)
> at org.eclipse.ui.internal.WorkbenchWindow$6.run(WorkbenchWindow.java:867)
> at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
> at org.eclipse.ui.internal.WorkbenchWindow.close(WorkbenchWindow.java:865)
> at org.eclipse.jface.window.WindowManager.close(WindowManager.java:109)
> at org.eclipse.ui.internal.Workbench$18.run(Workbench.java:1114)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.ui.internal.Workbench.busyClose(Workbench.java:1111)
> at org.eclipse.ui.internal.Workbench.access$15(Workbench.java:1040)
> at org.eclipse.ui.internal.Workbench$25.run(Workbench.java:1284)
> at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
> at org.eclipse.ui.internal.Workbench.close(Workbench.java:1282)
> at org.eclipse.ui.internal.Workbench.close(Workbench.java:1254)
> at org.eclipse.ui.internal.testing.WorkbenchTestable$2.run(WorkbenchTestable.java:124)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3563)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3212)
> at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2701)
> at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2665)
> at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2499)
> at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:679)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:668)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:123)
> at org.eclipse.swtbot.eclipse.core.UITestApplication.start(UITestApplication.java:54)
> 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:344)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1410)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1386)
--
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