Mark Hobson wrote:
2008/8/13 Oleg Gusakov <[EMAIL PROTECTED]>:
Mark - this is the same if one excludes repositories and lives within
pre-existing version set: like Maven having only local repo and OSGi having
one OBR file.
If we add a variable - repositories that constantly change, then we start
wondering what to do and OSGi joins this discussion as soon as they add this
feature.
I'm not quite sure that I understand the scenario you're describing
here? Aren't the repositories defined with the pom and so are
constant?
Repositories are [pseudo]constant, their contents are not. So today I
may resolve to a-1.1.jar, tomorrow it might already resolve to
a-2.0.jar. In this regard OSGi is a little more restrictive as it has a
definite set of bundles to resolve from, but this set may also change
and various OSGi implementations deal with this differently. So in
general - they face the same issue.
Pseudo constant - if tomorrow a build engineer decides to add two more
repos to you parent's parent POM, you suddenly have to deal with a
broader spectrum of possible candidates.
I will start a page on version ranges, where I'll try to capture the
version range design and issues around it - it's empty, but not for
long: http://docs.codehaus.org/x/twDPBQ .
I am convinced we can bake something decent !
Oleg
