Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 204410 - CDO test needs Net4j test dependency
Summary: CDO test needs Net4j test dependency
Status: CLOSED FIXED
Alias: None
Product: EMF
Classification: Modeling
Component: cdo.core (show other bugs)
Version: 1.0   Edit
Hardware: PC Windows XP
: P1 blocker (vote)
Target Milestone: ---   Edit
Assignee: Eike Stepper CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-09-24 03:09 EDT by Eike Stepper CLA
Modified: 2010-06-29 09:21 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Eike Stepper CLA 2007-09-24 03:09:41 EDT
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 ;-(
Comment 1 Eike Stepper CLA 2007-09-24 07:48:31 EDT
Fixed with different approach:
The test features of both Net4j and CDO are now included in their SDKs.
Comment 2 Eike Stepper CLA 2007-09-24 09:02:27 EDT
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?
Comment 3 Eike Stepper CLA 2007-09-24 09:09:02 EDT
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?
Comment 4 Nick Boldt CLA 2007-09-24 11:36:15 EDT
(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
Comment 5 Eike Stepper CLA 2007-09-24 11:55:53 EDT
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.
Comment 6 Nick Boldt CLA 2007-09-24 14:27:46 EDT
(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.
Comment 7 Eike Stepper CLA 2007-10-16 05:21:54 EDT
Fixed in I200710101632.
Comment 8 Nick Boldt CLA 2008-01-28 16:44:38 EST
Move to verified as per bug 206558.
Comment 9 Eike Stepper CLA 2008-06-10 02:28:42 EDT
Reversioned due to graduation
Comment 10 Eike Stepper CLA 2008-09-11 13:48:50 EDT
CLOSING