[JBoss JIRA] (JBIDE-14537) BrowserSim 4.1.0.Beta1 - JUnit failure WebKitTests.testWebKitSetDefaultUserAgent
by Konstantin Marmalyukov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14537?page=com.atlassian.jira.plugi... ]
Konstantin Marmalyukov commented on JBIDE-14537:
------------------------------------------------
But the better way is having WebKit installed on Build server:)
Btw, what about progress on this task?
> BrowserSim 4.1.0.Beta1 - JUnit failure WebKitTests.testWebKitSetDefaultUserAgent
> --------------------------------------------------------------------------------
>
> Key: JBIDE-14537
> URL: https://issues.jboss.org/browse/JBIDE-14537
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: browsersim
> Affects Versions: 4.1.0.Beta1
> Reporter: Yahor Radtsevich
> Assignee: Nick Boldt
> Fix For: 4.1.0.Beta2
>
>
> https://hudson.jboss.org/hudson/view/JBossTools/view/JBossTools_4.1.keple...
> org.jboss.tools.vpe.browsersim.browser.test.WebKitTests.testWebKitSetDefaultUserAgent
> {code}
> org.eclipse.swt.SWTError: No more handles
> at org.eclipse.swt.SWT.error(SWT.java:4418)
> at org.eclipse.swt.SWT.error(SWT.java:4307)
> at org.eclipse.swt.SWT.error(SWT.java:4278)
> at org.eclipse.swt.browser.Browser.<init>(Browser.java:103)
> at org.jboss.tools.vpe.browsersim.browser.BrowserSimBrowser.<init>(BrowserSimBrowser.java:9)
> at org.jboss.tools.vpe.browsersim.browser.AbstractWebKitBrowser.<init>(AbstractWebKitBrowser.java:24)
> at org.jboss.tools.vpe.browsersim.browser.internal.WebKitBrowser_gtk_linux_x86_64.<init>(WebKitBrowser_gtk_linux_x86_64.java:38)
> at org.jboss.tools.vpe.browsersim.browser.WebKitBrowserFactory.createBrowser(WebKitBrowserFactory.java:36)
> at org.jboss.tools.vpe.browsersim.browser.test.WebKitTests.testWebKitSetDefaultUserAgent(WebKitTests.java:39)
> 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 junit.framework.TestCase.runTest(TestCase.java:176)
> at junit.framework.TestCase.runBare(TestCase.java:141)
> at junit.framework.TestResult$1.protect(TestResult.java:122)
> at junit.framework.TestResult.runProtected(TestResult.java:142)
> at junit.framework.TestResult.run(TestResult.java:125)
> at junit.framework.TestCase.run(TestCase.java:129)
> at junit.framework.TestSuite.runTest(TestSuite.java:255)
> at junit.framework.TestSuite.run(TestSuite.java:250)
> at junit.framework.TestSuite.runTest(TestSuite.java:255)
> at junit.framework.TestSuite.run(TestSuite.java:250)
> at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:84)
> at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:53)
> at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:123)
> at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:104)
> 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.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:164)
> at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:110)
> at org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:175)
> at org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcess(SurefireStarter.java:123)
> at org.eclipse.tycho.surefire.osgibooter.OsgiSurefireBooter.run(OsgiSurefireBooter.java:85)
> at org.eclipse.tycho.surefire.osgibooter.AbstractUITestApplication$1.run(AbstractUITestApplication.java:35)
> 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:3692)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3341)
> 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.tycho.surefire.osgibooter.UITestApplication.runApplication(UITestApplication.java:31)
> at org.eclipse.tycho.surefire.osgibooter.AbstractUITestApplication.run(AbstractUITestApplication.java:114)
> at org.eclipse.tycho.surefire.osgibooter.UITestApplication.start(UITestApplication.java:37)
> 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: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: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, 10 months
[JBoss JIRA] (JBIDE-14537) BrowserSim 4.1.0.Beta1 - JUnit failure WebKitTests.testWebKitSetDefaultUserAgent
by Yahor Radtsevich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14537?page=com.atlassian.jira.plugi... ]
Yahor Radtsevich commented on JBIDE-14537:
------------------------------------------
We could use something like {{@Category}} annotation ([see example|http://craigpardey.com/wp/2012/07/junit-categories-with-maven/]).
> BrowserSim 4.1.0.Beta1 - JUnit failure WebKitTests.testWebKitSetDefaultUserAgent
> --------------------------------------------------------------------------------
>
> Key: JBIDE-14537
> URL: https://issues.jboss.org/browse/JBIDE-14537
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: browsersim
> Affects Versions: 4.1.0.Beta1
> Reporter: Yahor Radtsevich
> Assignee: Nick Boldt
> Fix For: 4.1.0.Beta2
>
>
> https://hudson.jboss.org/hudson/view/JBossTools/view/JBossTools_4.1.keple...
> org.jboss.tools.vpe.browsersim.browser.test.WebKitTests.testWebKitSetDefaultUserAgent
> {code}
> org.eclipse.swt.SWTError: No more handles
> at org.eclipse.swt.SWT.error(SWT.java:4418)
> at org.eclipse.swt.SWT.error(SWT.java:4307)
> at org.eclipse.swt.SWT.error(SWT.java:4278)
> at org.eclipse.swt.browser.Browser.<init>(Browser.java:103)
> at org.jboss.tools.vpe.browsersim.browser.BrowserSimBrowser.<init>(BrowserSimBrowser.java:9)
> at org.jboss.tools.vpe.browsersim.browser.AbstractWebKitBrowser.<init>(AbstractWebKitBrowser.java:24)
> at org.jboss.tools.vpe.browsersim.browser.internal.WebKitBrowser_gtk_linux_x86_64.<init>(WebKitBrowser_gtk_linux_x86_64.java:38)
> at org.jboss.tools.vpe.browsersim.browser.WebKitBrowserFactory.createBrowser(WebKitBrowserFactory.java:36)
> at org.jboss.tools.vpe.browsersim.browser.test.WebKitTests.testWebKitSetDefaultUserAgent(WebKitTests.java:39)
> 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 junit.framework.TestCase.runTest(TestCase.java:176)
> at junit.framework.TestCase.runBare(TestCase.java:141)
> at junit.framework.TestResult$1.protect(TestResult.java:122)
> at junit.framework.TestResult.runProtected(TestResult.java:142)
> at junit.framework.TestResult.run(TestResult.java:125)
> at junit.framework.TestCase.run(TestCase.java:129)
> at junit.framework.TestSuite.runTest(TestSuite.java:255)
> at junit.framework.TestSuite.run(TestSuite.java:250)
> at junit.framework.TestSuite.runTest(TestSuite.java:255)
> at junit.framework.TestSuite.run(TestSuite.java:250)
> at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:84)
> at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:53)
> at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:123)
> at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:104)
> 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.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:164)
> at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:110)
> at org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:175)
> at org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcess(SurefireStarter.java:123)
> at org.eclipse.tycho.surefire.osgibooter.OsgiSurefireBooter.run(OsgiSurefireBooter.java:85)
> at org.eclipse.tycho.surefire.osgibooter.AbstractUITestApplication$1.run(AbstractUITestApplication.java:35)
> 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:3692)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3341)
> 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.tycho.surefire.osgibooter.UITestApplication.runApplication(UITestApplication.java:31)
> at org.eclipse.tycho.surefire.osgibooter.AbstractUITestApplication.run(AbstractUITestApplication.java:114)
> at org.eclipse.tycho.surefire.osgibooter.UITestApplication.start(UITestApplication.java:37)
> 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: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: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, 10 months
[JBoss JIRA] (JBIDE-14663) Source lookup dialog shown twice on maven projects
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14663?page=com.atlassian.jira.plugi... ]
Fred Bricon commented on JBIDE-14663:
-------------------------------------
Your video shows m2e messing with a non-maven project. I can't reproduce that on my side. But what you see is likely a bug. I don't think this is supposed to happen on non-maven projects and should be reported as a bug.
> Source lookup dialog shown twice on maven projects
> --------------------------------------------------
>
> Key: JBIDE-14663
> URL: https://issues.jboss.org/browse/JBIDE-14663
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: maven
> Affects Versions: 4.1.0.Beta1
> Reporter: Fred Bricon
> Assignee: Fred Bricon
> Labels: respin-b
> Fix For: 4.1.0.Beta1
>
>
> Source lookup dialog is shown twice on maven projects : http://screencast.com/t/3yESat96FIw
> I think our source lookup should ignore projects with the maven nature, since a m2e's source lookup mechanism is already running in the background.
> If maven nature is enabled AND source is set but missing THEN, it'd be ok to show our own stuff
--
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, 10 months
[JBoss JIRA] (JBIDE-14691) remove *Express* from class names
by Andre Dietisheim (JIRA)
Andre Dietisheim created JBIDE-14691:
----------------------------------------
Summary: remove *Express* from class names
Key: JBIDE-14691
URL: https://issues.jboss.org/browse/JBIDE-14691
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: openshift
Affects Versions: 4.1.0.Beta2
Reporter: Andre Dietisheim
Assignee: Andre Dietisheim
Fix For: 4.1.0.Beta2
We still have plenty of classes which have *Express* in the name. This is back from the times when there was an OpenShift Express edition. We should remove those since those class names are nothing one would expect and make maintaining code just harder.
--
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, 10 months
[JBoss JIRA] (JBIDE-14537) BrowserSim 4.1.0.Beta1 - JUnit failure WebKitTests.testWebKitSetDefaultUserAgent
by Yahor Radtsevich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14537?page=com.atlassian.jira.plugi... ]
Yahor Radtsevich updated JBIDE-14537:
-------------------------------------
Fix Version/s: 4.1.0.Beta2
(was: 4.1.0.Beta1)
> BrowserSim 4.1.0.Beta1 - JUnit failure WebKitTests.testWebKitSetDefaultUserAgent
> --------------------------------------------------------------------------------
>
> Key: JBIDE-14537
> URL: https://issues.jboss.org/browse/JBIDE-14537
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: browsersim
> Affects Versions: 4.1.0.Beta1
> Reporter: Yahor Radtsevich
> Assignee: Nick Boldt
> Fix For: 4.1.0.Beta2
>
>
> https://hudson.jboss.org/hudson/view/JBossTools/view/JBossTools_4.1.keple...
> org.jboss.tools.vpe.browsersim.browser.test.WebKitTests.testWebKitSetDefaultUserAgent
> {code}
> org.eclipse.swt.SWTError: No more handles
> at org.eclipse.swt.SWT.error(SWT.java:4418)
> at org.eclipse.swt.SWT.error(SWT.java:4307)
> at org.eclipse.swt.SWT.error(SWT.java:4278)
> at org.eclipse.swt.browser.Browser.<init>(Browser.java:103)
> at org.jboss.tools.vpe.browsersim.browser.BrowserSimBrowser.<init>(BrowserSimBrowser.java:9)
> at org.jboss.tools.vpe.browsersim.browser.AbstractWebKitBrowser.<init>(AbstractWebKitBrowser.java:24)
> at org.jboss.tools.vpe.browsersim.browser.internal.WebKitBrowser_gtk_linux_x86_64.<init>(WebKitBrowser_gtk_linux_x86_64.java:38)
> at org.jboss.tools.vpe.browsersim.browser.WebKitBrowserFactory.createBrowser(WebKitBrowserFactory.java:36)
> at org.jboss.tools.vpe.browsersim.browser.test.WebKitTests.testWebKitSetDefaultUserAgent(WebKitTests.java:39)
> 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 junit.framework.TestCase.runTest(TestCase.java:176)
> at junit.framework.TestCase.runBare(TestCase.java:141)
> at junit.framework.TestResult$1.protect(TestResult.java:122)
> at junit.framework.TestResult.runProtected(TestResult.java:142)
> at junit.framework.TestResult.run(TestResult.java:125)
> at junit.framework.TestCase.run(TestCase.java:129)
> at junit.framework.TestSuite.runTest(TestSuite.java:255)
> at junit.framework.TestSuite.run(TestSuite.java:250)
> at junit.framework.TestSuite.runTest(TestSuite.java:255)
> at junit.framework.TestSuite.run(TestSuite.java:250)
> at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:84)
> at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:53)
> at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:123)
> at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:104)
> 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.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:164)
> at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:110)
> at org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:175)
> at org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcess(SurefireStarter.java:123)
> at org.eclipse.tycho.surefire.osgibooter.OsgiSurefireBooter.run(OsgiSurefireBooter.java:85)
> at org.eclipse.tycho.surefire.osgibooter.AbstractUITestApplication$1.run(AbstractUITestApplication.java:35)
> 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:3692)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3341)
> 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.tycho.surefire.osgibooter.UITestApplication.runApplication(UITestApplication.java:31)
> at org.eclipse.tycho.surefire.osgibooter.AbstractUITestApplication.run(AbstractUITestApplication.java:114)
> at org.eclipse.tycho.surefire.osgibooter.UITestApplication.start(UITestApplication.java:37)
> 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: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: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, 10 months
[JBoss JIRA] (JBIDE-14663) Source lookup dialog shown twice on maven projects
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14663?page=com.atlassian.jira.plugi... ]
Fred Bricon commented on JBIDE-14663:
-------------------------------------
Jars out of the maven classpath library are irrelevant. Whoever does that is shooting himself in the foot. We don't have to support that scenario.
You already proved source attachments couldn't use variables, so be it. In the case of maven projects, it's not important since the hardcoded path is stored at the workspace level, not in .classpath that is shared among developers.
Since we have not other way to provide source attachments, we warn the users about hardcoded paths. I think it's acceptable.
The double dialog issue was not caused/related to maven. However, the screencast clearly shows maven does its thing in the background, while we ask the user if we should proceed. We have *two* source lookup mechanisms running concurrently. This is wrong IMO, hence the reason why I wanted to treat maven differently.
I understand the advantages of your source lookup mechanism over m2e's, really, but I've never seen any bug report about mismatch sources in m2e. If that was really a problem, source validation could also be implemented directly in m2e.
So I'm -0 about the "Enable Source Lookup for maven projects".
> Source lookup dialog shown twice on maven projects
> --------------------------------------------------
>
> Key: JBIDE-14663
> URL: https://issues.jboss.org/browse/JBIDE-14663
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: maven
> Affects Versions: 4.1.0.Beta1
> Reporter: Fred Bricon
> Assignee: Fred Bricon
> Labels: respin-b
> Fix For: 4.1.0.Beta1
>
>
> Source lookup dialog is shown twice on maven projects : http://screencast.com/t/3yESat96FIw
> I think our source lookup should ignore projects with the maven nature, since a m2e's source lookup mechanism is already running in the background.
> If maven nature is enabled AND source is set but missing THEN, it'd be ok to show our own stuff
--
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, 10 months
[JBoss JIRA] (TOOLSDOC-341) Review: QE to review Beta1 Release Notes
by Len DiMaggio (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-341?page=com.atlassian.jira.plug... ]
Len DiMaggio updated TOOLSDOC-341:
----------------------------------
Attachment: Screenshot.png
Section:
1.1. About JBoss Developer Studio
Text:
Additionally, each of the tools comprising JBoss Developer Studio has great
features to assist your application development:
Comment:
I think it would be better to refer to JBDS as a whole, as opposed a set of tools. Maybe this sentence can be reworded as:
Additionally, JBoss Developer Studio has great features to assist your application development:
------
Section:
1.2. Use Cases of JBoss Developer Studio
Text:
JBoss Developer Studio assists JEE developers by integrating JBoss technology and APIs in a single development environment. Here are a few ways that JBoss Developer Studio makes the work of a developer easier.
Comment:
Very small point - end with a ":" not a "."
------
Section:
1.2. Use Cases of JBoss Developer Studio
Text:
BrowserSim allows you to view your web applications on a variety of simulated mobile devices so that you can ensure they will be correct formatted.
Comment:
This is a small point. Can we change this to read: "correctly formatted"?
------
Chapter 2. New Features
You asked for input on this subject:
JBoss Central
NeedInfo: Cheat sheets for 'Start from a sample' project wizards are now automatically opened when projects are created and the cheat sheets can be subsequently accessed via the Show In option in project context menus.
See the attached screenshot for an illustration on what this looks like.
and:
JBoss Server Tools
NeedInfo: Additionally, you can choose to either stop or undeploy an
application from the server via the administrative console.
I'm not sure what your question is here. Users can deploy/undeploy applications to servers from either inside JBDS, or from the Admin Console provided by EAP or SOA-P.
> Review: QE to review Beta1 Release Notes
> ----------------------------------------
>
> Key: TOOLSDOC-341
> URL: https://issues.jboss.org/browse/TOOLSDOC-341
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: Release Notes
> Affects Versions: 4.1.0
> Reporter: Michelle Murray
> Assignee: Jiri Peterka
> Fix For: 4.1.0
>
> Attachments: Red_Hat_JBoss_Developer_Studio-7.0-Release_Notes_7.0.0-en-US.pdf, Screenshot.png
>
>
> *Please review* the Beta1 Release Notes document:
> 1) Are new features correctly documented?
> 2) Are there any new features that are missing?
> 3) Are there any JIRAs for resolved and unresolved bugs missing? Queries used were: Resolved = https://issues.jboss.org/issues/?filter=12319302 and Unresolved = https://issues.jboss.org/issues/?filter=12319301
> *Please give feedback* as comments in this JIRA, to assist tracking. The doc is available here as a pdf. Alternatively, the doc is also available on other formats at http://documentation-devel.engineering.redhat.com/docs/en-US/Red_Hat_JBos...
> *To make this document better*, we could do with culling the list of JIRAs down to those that need to be included in release notes. This requires someone to go through the JIRA list manually and set the 'Affects' field to 'Release Notes'. This task will have to be done for GA release notes anyway.
--
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, 10 months