Community
Participate
Working Groups
Reason: o.e.e.cdo.tests has a dependency on o.e.net4j.tests which is not part of the Net4j SDK. I have temporarily removed the dependency and copied the related classes to cdo.tests. I fear we need an additional build dep on CDO ;-(
Fixed with different approach: The test features of both Net4j and CDO are now included in their SDKs.
New problem: CDO test code can't find Net4j test code: http://emft.eclipse.org/modeling/emft/cdo/downloads/drops/0.8.0/N200709240853/buildlog.txt Nick, do you have an idea what's going on?
Hmm, this reminds me a bit to the obscure problems with unresolved symbols we've had several times. If I remember correctly it was related to the order of included features within the SDK feature. This somehow led to correct or incorrect build order. Can this be the cause here, too?
(In reply to comment #3) > Hmm, this reminds me a bit to the obscure problems with unresolved symbols > we've had several times. If I remember correctly it was related to the order of > included features within the SDK feature. This somehow led to correct or > incorrect build order. Can this be the cause here, too? > http://wiki.eclipse.org/Modeling_Project_Releng/Building_Zips_And_Jars#Build_Problems_.26_Solutions
But here it seems a bit different. The Net4j sdk is not part of the CDO sdk. It is a build dependency url and should thus be expanded to binary plugins directly from the sdk zip before any compiler runs.
(In reply to comment #5) > But here it seems a bit different. The Net4j sdk is not part of the CDO sdk. It > is a build dependency url and should thus be expanded to binary plugins > directly from the sdk zip before any compiler runs. It's probably the way the sdk contains the test plugins, or the order you're compiling them (feature.xml) You could take a different approach and see what Christian did in order to get the EMF examples into his build environment: /org.eclipse.emf.query.releng/builder/examples/customTargets.xml#postSetup /org.eclipse.emf.query.releng/builder/sdk/customTargets.xml#postSetup /org.eclipse.emf.query.releng/builder/sdk/customTargets.xml#preFetch Or, you could start running Net4j and CDO as a single build, which generates 8 zips (4 each). It would compile everything in one go, and then you'd just have to write some simple ant stuff to handle the repackaging (see emf.releng's buildAll.xml as an example -- we now build 3 SDKs (EMF, SDO, XSD) via a single build, the repack those as the runtime zips.
Fixed in I200710101632.
Move to verified as per bug 206558.
Reversioned due to graduation
CLOSING