[JBoss JIRA] Created: (JBIDE-5809) Add clearer error message when edi mapping model schema version is not supported.
by Daniel Bevenius (JIRA)
Add clearer error message when edi mapping model schema version is not supported.
---------------------------------------------------------------------------------
Key: JBIDE-5809
URL: https://jira.jboss.org/jira/browse/JBIDE-5809
Project: Tools (JBoss Tools)
Issue Type: Task
Components: smooks
Reporter: Daniel Bevenius
Attachments: Screen shot 2010-02-08 at 1.48.16 PM.png
When using a edi mapping model that has a higher schema version number then the Smooks runtime bundled with the eclipse plugin supports, the error message is simply:
Check Input Task configuration. Error creating Input Model from Sample Input Data. Error "..." I'll attached a screenshot of the error.
I noticed this when trying the Smook plugin using the edi-to-java example in Smooks trunk. This example uses the following schema version:
http://www.milyn.org/schema/edi-message-mapping-1.3.xsd
and the version of Smooks bundled with the eclipse plugin only supports 1.2 (I think).
I asked Tom about this and he said that there already is some checking of the versions and perhaps this is only a case on making the error message a little more informative.
The version of the Smooks plugin I used is: 1.1.0.v201002050900N-H208-CR2.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] (JBIDE-11802) ClassNotFound: WrappedException, when opening smooks configuration with ''<esbr:routeBean/>'
by Jason Shepherd (JIRA)
Jason Shepherd created JBIDE-11802:
--------------------------------------
Summary: ClassNotFound: WrappedException, when opening smooks configuration with ''<esbr:routeBean/>'
Key: JBIDE-11802
URL: https://issues.jboss.org/browse/JBIDE-11802
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: smooks
Affects Versions: 3.2.2.Final
Environment: JBoss Developer Studio 4.1.2, and 4.1.1
java.version=1.6.0_24
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
Framework arguments: -product com.jboss.jbds.product.product
Command-line arguments: -os linux -ws gtk -arch x86_64 -product com.jboss.jbds.product.product
Reporter: Jason Shepherd
Assignee: Brian Fitzpatrick
Priority: Minor
Smooks editor shows the following error at the top of the guided smooks editor window:
"org.eclipse.emf.common.util.WrappedException: java.lang.ClassNotFoundException"
It only happens when we include the following in the Smooks configuration:
" <esbr:routeBean beanIdRef="orderItemFragment" toServiceCategory="QS" toServiceName="Receiver" routeOnElement="order-item">
<condition idRef="routeItem" />
</esbr:routeBean>"
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] (JBIDE-13005) test failure in org.jboss.tools.common.el.core.test.CommonELAllTests
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-13005:
----------------------------------
Summary: test failure in org.jboss.tools.common.el.core.test.CommonELAllTests
Key: JBIDE-13005
URL: https://issues.jboss.org/browse/JBIDE-13005
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: common/jst/core
Affects Versions: 4.0.0.Beta2
Reporter: Nick Boldt
Assignee: Alexey Kazakov
Fix For: 4.0.0.Beta2
{code}
cd ~/jbosstools-base
mvn clean install -DtychoVersion=0.15.0 | tee log_tycho0150.txt
{code}
{code}
[INFO] org.jboss.tools.common.el.core.test ............... FAILURE [56.523s]
[INFO] org.jboss.tools.common.all.test.feature ........... SKIPPED
[INFO] base.site ......................................... SKIPPED
[ERROR] Failed to execute goal org.eclipse.tycho:tycho-surefire-plugin:0.15.0:test (default-test) on project org.jboss.tools.common.el.core.test: There are test failures.
[ERROR]
[ERROR] Please refer to /home/nboldt/eclipse/workspace-jboss/jbosstools-github/base/common/tests/org.jboss.tools.common.el.core.test/target/surefire-reports for the individual test results.
{code}
{code}
-------------------------------------------------------------------------------
Test set: org.jboss.tools.common.el.core.test.CommonELAllTests
-------------------------------------------------------------------------------
Tests run: 48, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 51.136 sec <<< FAILURE!
testTokenizerOnCorrectEL(org.jboss.tools.common.el.core.test.ELParserTest) Time elapsed: 0.028 sectestJBIDE3132(org.jboss.tools.common.el.core.test.ELParserTest) Time elapsed: 0.024 sectestElEmptyOperator(org.jboss.tools.common.el.core.test.ELParserTest) Time elapsed: 0 sectestElLogicalNotOperators(org.jboss.tools.common.el.core.test.ELParserTest) Time elapsed: 0 sectestElLogicalAndOperators(org.jboss.tools.common.el.core.test.ELParserTest) Time elapsed: 0.001 sectestElLogicalOrOperators(org.jboss.tools.common.el.core.test.ELParserTest) Time elapsed: 0.001 sectestElConditionalOperator(org.jboss.tools.common.el.core.test.ELParserTest) Time elapsed: 0 sectestElRelationalOperator(org.jboss.tools.common.el.core.test.ELParserTest) Time elapsed: 0.005 sectestElArithmeticOperators(org.jboss.tools.common.el.core.test.ELParserTest) Time elapsed: 0.005 sectestElLiteralExpressions(org.jboss.tools.common.el.core.test.ELParserTest) Time elapsed: 0.001 sectestElReferencesObjectProperties(org.jboss.tools.common.el.core.test.ELParserTest) Time elapsed: 0.001 sectestElSimpleTypes(org.jboss.tools.common.el.core.test.ELParserTest) Time elapsed: 0.001 sectestReservedWordAnd(org.jboss.tools.common.el.core.test.ELParserTest) Time elapsed: 0.003 sectestReservedWordOr(org.jboss.tools.common.el.core.test.ELParserTest) Time elapsed: 0.001 sectestReservedWordNot(org.jboss.tools.common.el.core.test.ELParserTest) Time elapsed: 0.001 sectestReservedWordEq(org.jboss.tools.common.el.core.test.ELParserTest) Time elapsed: 0.001 sectestReservedWordNe(org.jboss.tools.common.el.core.test.ELParserTest) Time elapsed: 0 sectestReservedWordLt(org.jboss.tools.common.el.core.test.ELParserTest) Time elapsed: 0.001 sectestReservedWordGt(org.jboss.tools.common.el.core.test.ELParserTest) Time elapsed: 0 sectestReservedWordLe(org.jboss.tools.common.el.core.test.ELParserTest) Time elapsed: 0.001 sectestReservedWordGe(org.jboss.tools.common.el.core.test.ELParserTest) Time elapsed: 0 sectestReservedWordTrue(org.jboss.tools.common.el.core.test.ELParserTest) Time elapsed: 0.001 sectestReservedWordFalse(org.jboss.tools.common.el.core.test.ELParserTest) Time elapsed: 0 sectestReservedWordNull(org.jboss.tools.common.el.core.test.ELParserTest) Time elapsed: 0 sectestReservedWordInstanceof(org.jboss.tools.common.el.core.test.ELParserTest) Time elapsed: 0.001 sectestReservedWordEmpty(org.jboss.tools.common.el.core.test.ELParserTest) Time elapsed: 0 sectestReservedWordDiv(org.jboss.tools.common.el.core.test.ELParserTest) Time elapsed: 0.001 sectestReservedWordMod(org.jboss.tools.common.el.core.test.ELParserTest) Time elapsed: 0 sectestComplexMath(org.jboss.tools.common.el.core.test.ELParserTest) Time elapsed: 0.001 sectestComplexInvocation(org.jboss.tools.common.el.core.test.ELParserTest) Time elapsed: 0 sectestSeveralELInstances(org.jboss.tools.common.el.core.test.ELParserTest) Time elapsed: 0 sectestElInParenthesis(org.jboss.tools.common.el.core.test.ELParserTest) Time elapsed: 0 sectestTokenizerOnIncorrectEL(org.jboss.tools.common.el.core.test.ELParserTest) Time elapsed: 0.002 sectestLexemas(org.jboss.tools.common.el.core.test.ELParserTest) Time elapsed: 0.001 sectestMultiThreadAccess(org.jboss.tools.common.el.core.test.ELParserTest) Time elapsed: 1.207 sectestELModel(org.jboss.tools.common.el.core.test.ELModelTest) Time elapsed: 0.002 sectestInvokingMethodOnExpressionInParenthesis(org.jboss.tools.common.el.core.test.ELModelTest) Time elapsed: 0 sectestTagLibraryFunctionInvocation(org.jboss.tools.common.el.core.test.ELModelTest) Time elapsed: 0 sectestRelevanceCheck(org.jboss.tools.common.el.core.test.RelevanceCheckTest) Time elapsed: 18.195 sectestSetFile(org.jboss.tools.common.el.core.test.resolver.ElVarSearcherTest) Time elapsed: 0.029 sectestFindAllVarsIFileInt(org.jboss.tools.common.el.core.test.resolver.ElVarSearcherTest) Time elapsed: 0.447 sectestGetInstance(org.jboss.tools.common.el.core.test.resolver.ELResolverFactoryManagerTest) Time elapsed: 0.001 sectestGetResolvers(org.jboss.tools.common.el.core.test.resolver.ELResolverFactoryManagerTest) Time elapsed: 0.008 sectestTypeResolution(org.jboss.tools.common.el.core.test.resolver.TypeInfoCollectorTest) Time elapsed: 6.368 sec <<< FAILURE!
junit.framework.AssertionFailedError
at junit.framework.Assert.fail(Assert.java:48)
at junit.framework.Assert.assertTrue(Assert.java:20)
at junit.framework.Assert.assertNotNull(Assert.java:218)
at junit.framework.Assert.assertNotNull(Assert.java:211)
at org.jboss.tools.common.el.core.test.resolver.TypeInfoCollectorTest.testTypeResolution(TypeInfoCollectorTest.java:72)
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:168)
at junit.framework.TestCase.runBare(TestCase.java:134)
at junit.framework.TestResult$1.protect(TestResult.java:110)
at junit.framework.TestResult.runProtected(TestResult.java:128)
at junit.framework.TestResult.run(TestResult.java:113)
at junit.framework.TestCase.run(TestCase.java:124)
at junit.framework.TestSuite.runTest(TestSuite.java:243)
at junit.framework.TestSuite.run(TestSuite.java:238)
at junit.framework.TestSuite.runTest(TestSuite.java:243)
at junit.framework.TestSuite.run(TestSuite.java:238)
at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:83)
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:84)
at org.eclipse.tycho.surefire.osgibooter.HeadlessTestApplication.run(HeadlessTestApplication.java:21)
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.internal.app.EclipseAppContainer.callMethodWithException(EclipseAppContainer.java:587)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:198)
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:353)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:180)
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:629)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:584)
at org.eclipse.equinox.launcher.Main.run(Main.java:1438)
at org.eclipse.equinox.launcher.Main.main(Main.java:1414)
testCircularDependency(org.jboss.tools.common.el.core.test.resolver.TypeInfoCollectorTest) Time elapsed: 6.143 sectestOverridenMethod(org.jboss.tools.common.el.core.test.resolver.TypeInfoCollectorTest) Time elapsed: 6.142 sectestMissingInterface(org.jboss.tools.common.el.core.test.resolver.TypeInfoCollectorTest) Time elapsed: 6.122 sectestProperties(org.jboss.tools.common.el.core.test.resolver.TypeInfoCollectorTest) Time elapsed: 6.098 sec
{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
13 years, 4 months
[JBoss JIRA] (JBIDE-12966) jst tests failure
by Alexey Kazakov (JIRA)
Alexey Kazakov created JBIDE-12966:
--------------------------------------
Summary: jst tests failure
Key: JBIDE-12966
URL: https://issues.jboss.org/browse/JBIDE-12966
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: common/jst/core
Affects Versions: 4.0.0.CR1
Reporter: Alexey Kazakov
Assignee: Alexey Kazakov
Fix For: 4.0.0.CR1
{code}
#
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x00007fcda59ab5a0, pid=10407, tid=140523837720320
#
# JRE version: 7.0_09-b05
# Java VM: Java HotSpot(TM) 64-Bit Server VM (23.5-b02 mixed mode linux-amd64 compressed oops)
# Problematic frame:
# C [libwebkitgtk-1.0.so.0+0x14245a0] void WTF::freeOwnedGPtr<_GdkEvent>(_GdkEvent*)+0x15df0
#
# Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again
#
# An error report file with more information is saved as:
# /home/igels/Projects/jbt-4.0/contribution/jbosstools-jst/tests/org.jboss.tools.jst.web.ui.test/hs_err_pid10407.log
#
# If you would like to submit a bug report, please visit:
# http://bugreport.sun.com/bugreport/crash.jsp
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
{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
13 years, 4 months
[JBoss JIRA] (JBDS-2385) why do we have TWO .product files for JBDS?
by Nick Boldt (JIRA)
Nick Boldt created JBDS-2385:
--------------------------------
Summary: why do we have TWO .product files for JBDS?
Key: JBDS-2385
URL: https://issues.jboss.org/browse/JBDS-2385
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: installer
Affects Versions: 6.0.0.Beta2
Reporter: Nick Boldt
Assignee: Denis Golovin
Fix For: 6.0.0.CR1
I just found we have TWO .product files -- one that appears nearly empty and one that I think is more up to date. Should we delete one of them?
{code:title=https://svn.jboss.org/repos/devstudio/trunk/product/plugins/com.jboss.jbds.product/jbds.product}
commit f8e4aa2b4e5139bb64e78282e5161b1f5e495b4b
Author: nickboldt <nickboldt@ec4afb39-462b-0410-b77a-f9df8f7cdb54>
Date: Mon May 28 05:25:31 2012 +0000
release 5.0.0.CR1 for QE
git-svn-id: https://svn.jboss.org/repos/devstudio/trunk@9522 ec4afb39-462b-0410-b77a-f9df8f7cdb54
{code}
commit 7f5feefb82365dfa108d673edeec93636d95578c
Author: nickboldt <nickboldt@ec4afb39-462b-0410-b77a-f9df8f7cdb54>
Date: Thu Sep 6 17:15:47 2012 +0000
use https://devstudio.jboss.com/updates/6.0-staging/ instead of https://devstudio.jboss.com/updates/6.0/staging or https://devstudio.jboss.com/updates/5.0/staging (JBDS-2267)
git-svn-id: https://svn.jboss.org/repos/devstudio/trunk@10294 ec4afb39-462b-0410-b77a-f9df8f7cdb54
commit 6f690c113f18153f3a00f10bff090952dbb0e144
Author: dgolovin <dgolovin@ec4afb39-462b-0410-b77a-f9df8f7cdb54>
Date: Mon Jun 4 23:13:09 2012 +0000
JBDS-2176 Audit differences between Tycho-built installer (.updatesite job) and PDE-built installer (.product job)
removed
-Dosgi.bundles=reference:file:org.eclipse.equinox.simpleconfigurator_1.0.200.v20110815-1438.jar@1:start
from jbdevstudio.ini file, because it is not needed
git-svn-id: https://svn.jboss.org/repos/devstudio/trunk@9627 ec4afb39-462b-0410-b77a-f9df8f7cdb54
{code:title=https://svn.jboss.org/repos/devstudio/trunk/product/site/com.jboss.jbds.product}
{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
13 years, 4 months
[JBoss JIRA] (JBIDE-12845) org.jboss.tools.cdi.text.ext.test.InjectedPointHyperlinkDetectorTest failure
by Alexey Kazakov (JIRA)
Alexey Kazakov created JBIDE-12845:
--------------------------------------
Summary: org.jboss.tools.cdi.text.ext.test.InjectedPointHyperlinkDetectorTest failure
Key: JBIDE-12845
URL: https://issues.jboss.org/browse/JBIDE-12845
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: CDI
Reporter: Alexey Kazakov
Assignee: Daniel Azarov
Fix For: 4.0.0.Beta1
{code}
(org.jboss.tools.cdi.text.ext.test.InjectedPointHyperlinkDetectorTest) Time elapsed: 0.254 sec <<< FAILURE!
junit.framework.AssertionFailedError: Hyperlink - Show All Assignable Beans... not found next region - <Inject> 104 - 110 line - 7 position - 5
at junit.framework.Assert.fail(Assert.java:50)
at junit.framework.Assert.assertTrue(Assert.java:20)
at junit.framework.Assert.assertNotNull(Assert.java:218)
at org.jboss.tools.cdi.text.ext.test.CDIHyperlinkTestUtil.checkTestRegion(CDIHyperlinkTestUtil.java:212)
at org.jboss.tools.cdi.text.ext.test.CDIHyperlinkTestUtil.checkRegions(CDIHyperlinkTestUtil.java:179)
at org.jboss.tools.cdi.text.ext.test.CDIHyperlinkTestUtil.checkRegions(CDIHyperlinkTestUtil.java:100)
at org.jboss.tools.cdi.text.ext.test.InjectedPointHyperlinkDetectorTest.testInjectedPointHyperlinkDetectorWithComment(InjectedPointHyperlinkDetectorTest.java:169)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
{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
13 years, 4 months
[JBoss JIRA] (JBIDE-12931) Finish button should be disabled when server not selected
by Jaroslav Jankovič (JIRA)
Jaroslav Jankovič created JBIDE-12931:
-----------------------------------------
Summary: Finish button should be disabled when server not selected
Key: JBIDE-12931
URL: https://issues.jboss.org/browse/JBIDE-12931
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: Archives
Affects Versions: 4.0.0.Beta1
Reporter: Jaroslav Jankovič
Assignee: Rob Stryker
Fix For: 4.0.0.CR1
There is no need for Finish button in Archive Publish Dialog to be enabled, when no server is selected. It should be disabled.
--
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
13 years, 4 months
[JBoss JIRA] (JBIDE-12896) ConcurrentModificationException in CDICoreBuilder when importing existing application
by Xavier Coulon (JIRA)
Xavier Coulon created JBIDE-12896:
-------------------------------------
Summary: ConcurrentModificationException in CDICoreBuilder when importing existing application
Key: JBIDE-12896
URL: https://issues.jboss.org/browse/JBIDE-12896
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: CDI
Affects Versions: 4.0.0.Beta1
Reporter: Xavier Coulon
Assignee: Alexey Kazakov
Priority: Critical
Fix For: 4.0.0.Beta1
While working on resolving JBIDE-12690, I got the following error:
!MESSAGE Errors running builder 'CDI (Context and Dependency Injection) Builder' on project 'jboss-richfaces-webapp'.
!STACK 0
java.util.ConcurrentModificationException
at java.util.HashMap$HashIterator.nextEntry(HashMap.java:793)
at java.util.HashMap$KeyIterator.next(HashMap.java:828)
at org.jboss.tools.cdi.internal.core.impl.definition.DefinitionContext.copy(DefinitionContext.java:98)
at org.jboss.tools.cdi.internal.core.impl.definition.DefinitionContext.newWorkingCopy(DefinitionContext.java:340)
at org.jboss.tools.cdi.core.CDICoreBuilder.build(CDICoreBuilder.java:199)
at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:728)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:199)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:239)
at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:292)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:295)
at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:351)
at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:374)
at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:143)
at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:241)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
This exception occurred when I imported an existing project (jboss-richfaces-webapp) that had been created in another workspace.
--
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
13 years, 4 months
[JBoss JIRA] (JBIDE-12664) Process timeout in org.jboss.ide.eclipse.archives.test after 2400s
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-12664:
----------------------------------
Summary: Process timeout in org.jboss.ide.eclipse.archives.test after 2400s
Key: JBIDE-12664
URL: https://issues.jboss.org/browse/JBIDE-12664
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Archives
Affects Versions: 4.0.0.Alpha2
Reporter: Nick Boldt
Assignee: Rob Stryker
{code}
[INFO] org.jboss.ide.eclipse.archives.test ............... FAILURE [40:03.848s]
[ERROR] Failed to execute goal org.eclipse.tycho:tycho-surefire-plugin:0.15.0:test (default-test) on project org.jboss.ide.eclipse.archives.test: Error while executing platform: org.codehaus.plexus.util.cli.CommandLineTimeOutException: Error while executing external command, process killed. Process timeout out after 2400 seconds -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.eclipse.tycho:tycho-surefire-plugin:0.15.0:test (default-test) on project org.jboss.ide.eclipse.archives.test: Error while executing platform
{code}
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
--
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
13 years, 4 months