September 2013 - jbosstools-issues

[JBoss JIRA] (JBIDE-15160) support comparing bundle folders as well as bundle jars when comparing MD5 sums

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15160?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-15160: ------------------------------- Comment: was deleted (was: While you're applying PRs, this trivial update needs some love too: https://github.com/jbdevstudio/jbdevstudio-qa/pull/5) > support comparing bundle folders as well as bundle jars when comparing MD5 sums > ------------------------------------------------------------------------------- > > Key: JBIDE-15160 > URL: https://issues.jboss.org/browse/JBIDE-15160 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build, qa > Affects Versions: 4.1.0.CR1 > Reporter: Nick Boldt > Assignee: Pavol Srna > Priority: Critical > Fix For: 4.1.1.Alpha2 > > > Currently, versionwatch can only compare md5s for jars. Adding support for zipping folders to jars and then comparing those should be fairly simple to add. > We could also compare MD5s for plugins' manifest.mf files as well as the jars themselves. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15160) support comparing bundle folders as well as bundle jars when comparing MD5 sums

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15160?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-15160: ------------------------------------ Appears to be working: {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_Trunk/job/devstudio.versionwatch_71/36/console} 457581 [main] WARN org.jboss.tools.vwatch.service.EvaluationService - Bundle org.jboss.tools.central.themes.feature is a folder; must jar it to compare MD5 sums. {code} > support comparing bundle folders as well as bundle jars when comparing MD5 sums > ------------------------------------------------------------------------------- > > Key: JBIDE-15160 > URL: https://issues.jboss.org/browse/JBIDE-15160 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build, qa > Affects Versions: 4.1.0.CR1 > Reporter: Nick Boldt > Assignee: Pavol Srna > Priority: Critical > Fix For: 4.1.1.Alpha2 > > > Currently, versionwatch can only compare md5s for jars. Adding support for zipping folders to jars and then comparing those should be fairly simple to add. > We could also compare MD5s for plugins' manifest.mf files as well as the jars themselves. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2678) add EAP 6.1.1 to JBDS 7.1.0 installer

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2678?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-2678: ---------------------------------- http://download.devel.redhat.com/released/JBEAP-6/6.1.1/jboss-eap-6.1.1.zip is released, so I've added this to JBDS 7.1.0.Alpha1, Alpha2, and 8.0. https://github.com/jbdevstudio/jbdevstudio-product/pull/48 (jbosstools-4.1.x) https://github.com/jbdevstudio/jbdevstudio-product/pull/49 (master) https://github.com/jbdevstudio/jbdevstudio-product/pull/50 (jbosstools-4.1.1.Alpha1x) > add EAP 6.1.1 to JBDS 7.1.0 installer > ------------------------------------- > > Key: JBDS-2678 > URL: https://issues.jboss.org/browse/JBDS-2678 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: installer, requirements > Affects Versions: 7.0.0.GA > Reporter: Nick Boldt > Fix For: 7.1.0.Alpha1, 7.1.0.Alpha2 > > > EAP 6.1.1 is supposed to be out in September, so we should update the installers to include the new version at that time. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2678) add EAP 6.1.1 to JBDS 7.1.0 installer

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2678?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-2678: ----------------------------- CDW devel_ack: + (was: ?) > add EAP 6.1.1 to JBDS 7.1.0 installer > ------------------------------------- > > Key: JBDS-2678 > URL: https://issues.jboss.org/browse/JBDS-2678 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: installer, requirements > Affects Versions: 7.0.0.GA > Reporter: Nick Boldt > Fix For: 7.1.0.Alpha1, 7.1.0.Alpha2 > > > EAP 6.1.1 is supposed to be out in September, so we should update the installers to include the new version at that time. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2678) add EAP 6.1.1 to JBDS 7.1.0 installer

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2678?page=com.atlassian.jira.plugin.... ] Nick Boldt edited comment on JBDS-2678 at 9/6/13 11:03 AM: ----------------------------------------------------------- http://download.devel.redhat.com/released/JBEAP-6/6.1.1/jboss-eap-6.1.1.zip is released, so I've added this to JBDS 7.1.0.Alpha1, Alpha2, and 8.0. https://github.com/jbdevstudio/jbdevstudio-product/pull/50 (jbosstools-4.1.1.Alpha1x) https://github.com/jbdevstudio/jbdevstudio-product/pull/48 (jbosstools-4.1.x) https://github.com/jbdevstudio/jbdevstudio-product/pull/49 (master) was (Author: nickboldt): http://download.devel.redhat.com/released/JBEAP-6/6.1.1/jboss-eap-6.1.1.zip is released, so I've added this to JBDS 7.1.0.Alpha1, Alpha2, and 8.0. https://github.com/jbdevstudio/jbdevstudio-product/pull/48 (jbosstools-4.1.x) https://github.com/jbdevstudio/jbdevstudio-product/pull/49 (master) https://github.com/jbdevstudio/jbdevstudio-product/pull/50 (jbosstools-4.1.1.Alpha1x) > add EAP 6.1.1 to JBDS 7.1.0 installer > ------------------------------------- > > Key: JBDS-2678 > URL: https://issues.jboss.org/browse/JBDS-2678 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: installer, requirements > Affects Versions: 7.0.0.GA > Reporter: Nick Boldt > Fix For: 7.1.0.Alpha1, 7.1.0.Alpha2 > > > EAP 6.1.1 is supposed to be out in September, so we should update the installers to include the new version at that time. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2678) add EAP 6.1.1 to JBDS 7.1.0 installer

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2678?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-2678: ----------------------------- Summary: add EAP 6.1.1 to JBDS 7.1.0 installer (was: add EAP 6.1.1 to JBDS 7.0.x / 7.x installers) > add EAP 6.1.1 to JBDS 7.1.0 installer > ------------------------------------- > > Key: JBDS-2678 > URL: https://issues.jboss.org/browse/JBDS-2678 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: installer, requirements > Affects Versions: 7.0.0.GA > Reporter: Nick Boldt > Fix For: 7.1.x > > > EAP 6.1.1 is supposed to be out in September, so we should update the installers to include the new version at that time. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2678) add EAP 6.1.1 to JBDS 7.1.0 installer

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2678?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-2678: ----------------------------- Fix Version/s: 7.1.0.Alpha1 7.1.0.Alpha2 (was: 7.1.x) > add EAP 6.1.1 to JBDS 7.1.0 installer > ------------------------------------- > > Key: JBDS-2678 > URL: https://issues.jboss.org/browse/JBDS-2678 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: installer, requirements > Affects Versions: 7.0.0.GA > Reporter: Nick Boldt > Fix For: 7.1.0.Alpha1, 7.1.0.Alpha2 > > > EAP 6.1.1 is supposed to be out in September, so we should update the installers to include the new version at that time. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15459) org.jboss.tools.vpe.xulrunner.test.XPCOMTest.testGetSupportedInterfaces test failure on jenkins

by Konstantin Marmalyukov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15459?page=com.atlassian.jira.plugi... ] Konstantin Marmalyukov commented on JBIDE-15459: ------------------------------------------------ Locally tests passing fine. this ticked will be closed after next sucessfull build. > org.jboss.tools.vpe.xulrunner.test.XPCOMTest.testGetSupportedInterfaces test failure on jenkins > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-15459 > URL: https://issues.jboss.org/browse/JBIDE-15459 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: visual-page-editor-core > Affects Versions: 4.2.0.Alpha1 > Reporter: Konstantin Marmalyukov > Assignee: Konstantin Marmalyukov > > VPE master job #414 > Stacktrace: > java.lang.NullPointerException > at org.jboss.tools.vpe.xulrunner.editor.XulRunnerEditor.getDOMDocument(XulRunnerEditor.java:242) > at org.jboss.tools.vpe.xulrunner.test.XPCOMTest.testGetSupportedInterfaces(XPCOMTest.java:62) > 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:3717) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3366) > 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.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) -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15441) For JBIDE 4.1.1.Alpha1: Code Freeze + Branch [XULRunner]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15441?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-15441. ------------------------------ Resolution: Rejected Reopen and close as rejected, not done. > For JBIDE 4.1.1.Alpha1: Code Freeze + Branch [XULRunner] > -------------------------------------------------------- > > Key: JBIDE-15441 > URL: https://issues.jboss.org/browse/JBIDE-15441 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: xulrunner > Reporter: Nick Boldt > Assignee: Yahor Radtsevich > Priority: Blocker > Labels: task > Fix For: 4.1.1.Alpha1 > > > For JBIDE 4.1.1.Alpha1: Please perform the following tasks: > 0. If nothing has changed in your component since the least GA release on this branch, *Reject this JIRA*. > Otherwise: > 1. Update your root pom to use parent pom version 4.1.1.Alpha1-SNAPSHOT; > 2. Ensure you've built & run your plugin tests using the latest target platform version 4.31.0.Alpha1; > 3. Branch from your existing jbosstools-4.1.x branch into a new jbosstools-4.1.1.Alpha1x branch; > 4. Close (not resolve) this JIRA when done. [XULRunner] > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for XULRunner task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15459) org.jboss.tools.vpe.xulrunner.test.XPCOMTest.testGetSupportedInterfaces test failure on jenkins

by Konstantin Marmalyukov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15459?page=com.atlassian.jira.plugi... ] Konstantin Marmalyukov commented on JBIDE-15459: ------------------------------------------------ Looks like the reason of this failure is the same as failure of one of the test from JBIDE-15393. Test fails because xulRunnerEditor does not initialize and test begins. This kind of errors appears randomly and cannot be fixed. > org.jboss.tools.vpe.xulrunner.test.XPCOMTest.testGetSupportedInterfaces test failure on jenkins > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-15459 > URL: https://issues.jboss.org/browse/JBIDE-15459 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: visual-page-editor-core > Affects Versions: 4.2.0.Alpha1 > Reporter: Konstantin Marmalyukov > Assignee: Konstantin Marmalyukov > > VPE master job #414 > Stacktrace: > java.lang.NullPointerException > at org.jboss.tools.vpe.xulrunner.editor.XulRunnerEditor.getDOMDocument(XulRunnerEditor.java:242) > at org.jboss.tools.vpe.xulrunner.test.XPCOMTest.testGetSupportedInterfaces(XPCOMTest.java:62) > 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:3717) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3366) > 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.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) -- 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, 7 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 September 2013