Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Eclipse Process Manager (Stardust) » 1.1.2 build issue - needs missing product.home var ?
1.1.2 build issue - needs missing product.home var ? [message #1358179] Thu, 15 May 2014 21:41 Go to next message
Gudrun Koko is currently offline Gudrun KokoFriend
Messages: 20
Registered: January 2013
Junior Member

My 1.1.2 Stardust build from source fails on the first build step. In contrast, previous 1.1.0 build step finished successfully back in February 2014.

As usual
created a new build directory
ran git clone ... -b I_4_3
ran git checkout for
created and changed settings.xml.

First build step for 1.1.2 generates however below error:

build step used:
mvn install -f product/components-pom.xml -P stardust-build${STARDUST_TOOLS} -s ${STARDUST_TOOLS}/conf/m2/settings.xml

Error encountered:

[INFO] Total time: 1:55.946s
[INFO] Finished at: Wed May 14 14:36:45 MDT 2014
[INFO] Final Memory: 97M/234M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-resources-plugin:2.6:resources (default-resources) on project jcr-vfs: Error loading

property file '/home/gudrunk/build/stardust/components/jcr-vfs/${product.home}/product-parent/src/main/filters/' -> [Help 1]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.

Tried following fix to build step command - seems to work but build step fails nevertheless at some point later. So at this point I am unclear if above fix was correct and if yes what will fix errors encountered below. Increased memory settings

Changed build step - includes product.home
mvn install -f product/components-pom.xml -P stardust-build${STARDUST_TOOLS} -Dproduct.home=/home/gudrunk/build/stardust/product -s ${STARDUST_TOOLS}/conf/m2/settings.xml

14:06:46 ERROR [main ] ruct.sxml.DocumentBuilder - Unsupported StAX event type: 5
original document: <?xml version='1.0' encoding='UTF-8'?><structureddataroot xmlns:structureddata="uri:ag.carnot.structur
14:07:03 WARN [main ] DefaultPropertiesProvider - Property bundle '' not found. Current classloader = sun.misc.Launcher$AppClassLoader@12360be0
Running job '2.1.0' against item 'Model' with version '2.0.0'.

Upgrade to version 2.1.0 done.

Running job '2.2.0' against item 'Model' with version '2.1.0'.

Upgrade to version 2.2.0 done.

14:07:04 WARN [main ] patibility.el.Interpreter - Deprecated comparison symbol used: '=>'. Correct symbol is: '>='.
Tests run: 253, Failures: 0, Errors: 14, Skipped: 6, Time elapsed: 21.215 sec <<< FAILURE! - in org.eclipse.stardust.engine.SanityTestSuite
testConcurrentModificationViaSet(org.eclipse.stardust.common.config.GlobalParametersTest) Time elapsed: 0.687 sec <<< ERROR!
java.lang.OutOfMemoryError: unable to create new native thread
at java.lang.Thread.start0(Native Method)
at java.lang.Thread.start(
at java.util.concurrent.ThreadPoolExecutor.addThread(

Any help much appreciated


[Updated on: Fri, 16 May 2014 02:56]

Report message to a moderator

Re: 1.1.2 build issue - needs missing product.home var ? [message #1373863 is a reply to message #1358179] Thu, 22 May 2014 11:01 Go to previous message
Sven Rottstock is currently offline Sven RottstockFriend
Messages: 29
Registered: December 2012
Junior Member

sorry that you have build issues. As you may have noticed we have converted mostly all projects to native Maven projects. Unfortunately a lot of changes was needed to get the build working and we must introduce some new properties like product.home. Of course, we will update the Stardust WIKI as soon as we have finished the Maven migration task.

To fix your build issues it is sufficient to pass the -Dproduct.home=<root-stardust-checkout>/product parameter or in your case: -Dproduct.home=${STARDUST_TOOLS}/../product. This assumes that you have cloned the product Git repository besides of the clone. With the Maven Migration the test cases are automatically executed. To avoid this you can also pass the maven-surefire-plugin related Parameter -DskipTests=true

Previous Topic:Using Audit Trail Database
Next Topic:Eclipse does not start due to not finding the JRE and javaw.exe
Goto Forum:

Current Time: Wed May 04 06:26:23 GMT 2016

Powered by FUDForum. Page generated in 0.01883 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software