June 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-14499) Remove unnecessary tests files

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14499?page=com.atlassian.jira.plugi... ] Xavier Coulon resolved JBIDE-14499. ----------------------------------- Resolution: Done Done during JBIDE-14502 > Remove unnecessary tests files > ------------------------------- > > Key: JBIDE-14499 > URL: https://issues.jboss.org/browse/JBIDE-14499 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: livereload > Affects Versions: 4.1.0.Beta1 > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Fix For: 4.1.0.Beta2 > > > The JUnit tests rely on a sample project, but only a few files should be used, there's no need to so many images and java classes. -- 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

1
0
0 / 0

[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: ------------------------------------------------ [~nickboldt], it looks like #70 job passes fine. So, I think, after you kick master job this issue can be closed. Thank you for help. > 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

1
0
0 / 0

[JBoss JIRA] (JBIDE-14826) Seam2.3 tooling doesn't work correctly in JBDS 6.0.1 with EAP 6.1.0 runtime

by Tomas Remes (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14826?page=com.atlassian.jira.plugi... ] Tomas Remes updated JBIDE-14826: -------------------------------- Component/s: Seam 2 > Seam2.3 tooling doesn't work correctly in JBDS 6.0.1 with EAP 6.1.0 runtime > --------------------------------------------------------------------------- > > Key: JBIDE-14826 > URL: https://issues.jboss.org/browse/JBIDE-14826 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Seam 2 > Affects Versions: 4.0.1.Final > Environment: JBDS 6.0.1, WFK 2.3.0.ER1 Seam 2.3.1.Final (I guess it's same for the community latest release) > Reporter: Tomas Remes > > When you create Seam2.3 project with EAP 6.1.0 (tech preview) runtime, the EAP libraries won't be present on its classpath. This fact cause following problems, when you try to create new Seam form or reverse engineer entities from database: > "The type javax.validation.ConstraintViolation cannot be resolved. It is indirectly referenced from required .class files" > "The project was not built since its build path is incomplete. Cannot find the class file for javax.persistence.EntityManager." -- 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

1
0
0 / 0

[JBoss JIRA] (JBIDE-14826) Seam2.3 tooling doesn't work correctly in JBDS 6.0.1 with EAP 6.1.0 runtime

by Tomas Remes (JIRA)

Tomas Remes created JBIDE-14826: ----------------------------------- Summary: Seam2.3 tooling doesn't work correctly in JBDS 6.0.1 with EAP 6.1.0 runtime Key: JBIDE-14826 URL: https://issues.jboss.org/browse/JBIDE-14826 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 4.0.1.Final Environment: JBDS 6.0.1, WFK 2.3.0.ER1 Seam 2.3.1.Final (I guess it's same for the community latest release) Reporter: Tomas Remes When you create Seam2.3 project with EAP 6.1.0 (tech preview) runtime, the EAP libraries won't be present on its classpath. This fact cause following problems, when you try to create new Seam form or reverse engineer entities from database: "The type javax.validation.ConstraintViolation cannot be resolved. It is indirectly referenced from required .class files" "The project was not built since its build path is incomplete. Cannot find the class file for javax.persistence.EntityManager." -- 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

1
0
0 / 0

[JBoss JIRA] (JBIDE-14825) application creation/import wizard: have to manually create git folder if I dont want to use the default

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14825?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-14825: ------------------------------------- Priority: Minor (was: Major) > application creation/import wizard: have to manually create git folder if I dont want to use the default > -------------------------------------------------------------------------------------------------------- > > Key: JBIDE-14825 > URL: https://issues.jboss.org/browse/JBIDE-14825 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.1.0.Beta2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Minor > Fix For: 4.1.x > > Attachments: non-std-git-clone-location.png > > > steps to reproduce: > # ASSERT: make sure you have an account on OpenShift > # EXEC: launch app creation wizard > # EXEC: in 3nd page uncheck *use default clone destination* and type in some folder that does not exist yet > Result: > You have to create your folder on your own, the wizard wont help you, it'll just error > !non-std-git-clone-location.png! -- 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

1
0
0 / 0

[JBoss JIRA] (JBIDE-14825) application creation/import wizard: have to manually create git folder if I dont want to use the default

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14825?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-14825: ------------------------------------- Attachment: non-std-git-clone-location.png > application creation/import wizard: have to manually create git folder if I dont want to use the default > -------------------------------------------------------------------------------------------------------- > > Key: JBIDE-14825 > URL: https://issues.jboss.org/browse/JBIDE-14825 > 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.x > > Attachments: non-std-git-clone-location.png > > > steps to reproduce: > # ASSERT: make sure you have an account on OpenShift > # EXEC: launch app creation wizard > # EXEC: in 3nd page uncheck *use default clone destination* and type in some folder that does not exist yet > Result: > You have to create your folder on your own, the wizard wont help you, it'll just error > !non-std-git-clone-location.png! -- 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

1
0
0 / 0

[JBoss JIRA] (JBIDE-14825) application creation/import wizard: have to manually create git folder if I dont want to use the default

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-14825: ---------------------------------------- Summary: application creation/import wizard: have to manually create git folder if I dont want to use the default Key: JBIDE-14825 URL: https://issues.jboss.org/browse/JBIDE-14825 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.x steps to reproduce: # ASSERT: make sure you have an account on OpenShift # EXEC: launch app creation wizard # EXEC: in 3nd page uncheck *use default clone destination* and type in some folder that does not exist yet Result: You have to create your folder on your own, the wizard wont help you, it'll just error !non-std-git-clone-location.png! -- 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

1
0
0 / 0

[JBoss JIRA] (JBIDE-14824) Build/test failures

by Xavier Coulon (JIRA)

Xavier Coulon created JBIDE-14824: ------------------------------------- Summary: Build/test failures Key: JBIDE-14824 URL: https://issues.jboss.org/browse/JBIDE-14824 Project: Tools (JBoss Tools) Issue Type: Bug Components: livereload Affects Versions: 4.1.0.Beta2 Reporter: Xavier Coulon Assignee: Xavier Coulon Fix For: 4.1.0.Beta2 -- 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

1
0
0 / 0

[JBoss JIRA] (JBIDE-14823) Missing pom.xml in LiveReload UI plugin

by Xavier Coulon (JIRA)

Xavier Coulon created JBIDE-14823: ------------------------------------- Summary: Missing pom.xml in LiveReload UI plugin Key: JBIDE-14823 URL: https://issues.jboss.org/browse/JBIDE-14823 Project: Tools (JBoss Tools) Issue Type: Bug Components: livereload Affects Versions: 4.1.0.Beta2 Reporter: Xavier Coulon Assignee: Xavier Coulon Priority: Blocker Fix For: 4.1.0.Beta2 -- 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

1
0
0 / 0

[JBoss JIRA] (JBIDE-14822) Add missing icons in git repository

by Xavier Coulon (JIRA)

Xavier Coulon created JBIDE-14822: ------------------------------------- Summary: Add missing icons in git repository Key: JBIDE-14822 URL: https://issues.jboss.org/browse/JBIDE-14822 Project: Tools (JBoss Tools) Issue Type: Bug Components: livereload Affects Versions: 4.1.0.Beta2 Reporter: Xavier Coulon Assignee: Xavier Coulon Fix For: 4.1.0.Beta2 Icons are missing after splitting single plugin into a "core" + "ui" ones (JBIDE-14738) -- 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

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues June 2013