[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] conflicting dependencies to Orbit

Except manually checking the Orbit downloads page prior to each build because they may have dropped a new version, which forces me to update my Buckminster configuration (again manually)...
Actually, this is what I'm doing for each (major) build.

On Fri, Dec 17, 2010 at 11:32 AM, Eike Stepper <stepper@xxxxxxxxxx> wrote:
Am 17.12.2010 10:50, schrieb Nicolas Bros:


   You say "the bundles in the CDO update site depend on a [Orbit] bundle with a specific version". Wouldn't that happen through a Manifest.MF?


I don't understand the exact mechanism, but as I said, p2 seems to tighten dependency ranges.

In the CDO update site, I can see this (in downloads/modeling/emf/cdo/updates/4.0/4.0-M4-S201012140905/content.jar) :
<unit id='org.eclipse.net4j.db.derby.feature.group' version='4.0.0.v20101112-1636' singleton='false'>
   ....
<required namespace='org.eclipse.equinox.p2.iu' name='org.apache.derby' range='[10.5.1.1_201010140907,10.5.1.1_201010140907]'/>

The strict dependency was not specified in the Manifest.MF, but it was added by p2.
Does anybody have a suggestion what I can do?

Except manually checking the Orbit downloads page prior to each build because they may have dropped a new version, which forces me to update my Buckminster configuration (again manually)...
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev



--
Nicolas Bros
R&D
tel: 06 75 09 19 88
nbros@xxxxxxxxxxxxxxxx
nbros.mia@xxxxxxxxx
Mia-Software, 410 clos de la Courtine
93160 Noisy-le-Grand
http://www.mia-software.com
.: model driven agility :.