Skip to main content

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

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='' version='4.0.0.v20101112-1636' singleton='false'>
<required namespace='org.eclipse.equinox.p2.iu' name='org.apache.derby' range='[,]'/>

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)...



Back to the top