Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] Orbit build qualifiers changing with each build

Am 01.02.2011 09:45, schrieb Gunnar Wagenknecht:
Hi Eike,

Am 01.02.2011 08:16, schrieb Eike Stepper:
1) Why does Orbit change the qualifier with each build although I assume that nothng in these plugins has ever changed since their creation?
The qualifier only changes if the plug-in was re-tagged and released to
the build. This usually happens when an issue in the bundle manifest or
some other accompanying file (eg. about.html, etc.) has been detected
and fixed.
Okay, I've checked it for Derby and you're right: There was a non-code change.

As for your dependencies problem, your only option may be too not depend
on other features.
We don't do that. Our feature only *include* our own features and our own plugins and some Orbit plugins.

I really wonder why we have to include and thereby duplicate these Orbit bundles! Why can't Orbit maintain a p2 compsite repository with a single URL for all versions and why are we not allowed to add discovery URLs to our features? Am I spending days per milestone just to make the IP process happy?

Think of features as deployment descriptors.
Sometimes they fit, sometimes they doesn't.
I agree, *including* "foreign" stuff is the root of all evil.



For example, Gyrex neither depends on nor includes p2.core feature
because it references "org.apache.commons.logging". This is fine from a
p2 point of view. However, we don't ship this bundle but the SLF4J
wrapper which just provides the API. I therefore created my own
"provisioning.dependencies" feature. This allows you to reference and
ship the version/package that you prefer.


Back to the top