[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [cross-project-issues-dev] CDO M7 depends on Orbit M6
|
I suggest that I come up with an M7a build in an hour or so. Is that okay?
Yes, thank you.
Do you require *all* the CDO features? It seems that both (MongoDB as
well as Derby) are just additional implementation options. Maybe you can
just reference the CDO bundles you need?
MoDisco doesn't depend on all the CDO features. But I had trouble building with Buckminster, and I had to add references to features in the cspec in order to get it to build :
I don't know why I had to add these references; I would expect Buckminster to resolve the needed dependencies from the other built features automatically.
I suspect this is not the right way to do this, but it's the only way I've found at the moment.
It could be that MoDisco does not have a reference to your repo.
In fact it does, but I have set the Buckminster rmap so that it searches for org.eclipse.emf.cdo.* from the CDO update site, but other plug-ins not in the CDO packages from Orbit.
Because I assumed the Orbit plug-ins referenced by all projects would be present in the Orbit update site.
That seems to be the case for all plug-ins at the moment, apart from this "com.mongodb".
On Wed, May 4, 2011 at 11:49 AM, Gunnar Wagenknecht
<gunnar@xxxxxxxxxxxxxxx> wrote:
Am 04.05.2011 11:43, schrieb Eike Stepper:
> I have currently no clue why it is not found in our repository because I can definitely see it there. Does anybody else have an idea?
It could be that MoDisco does not have a reference to your repo.
Nicolas, where are you consuming CDO from? Note, you should not consume
CDO from the Indigo repo but directly from the CDO repo which has the
build contributed to Indigo. Otherwise it will be hard to make your
build reproducible if the Indigo repo changes (looses all the
milestones). But I don't remember the exact reason. There was a
discussion some time ago.
