Re: [orbit-dev] Bundle versions

[DJ Houghton <DJ_Houghton@xxxxxxxxxx>]

Ok, so the story going forward:
- use qualifiers in your bundle version (e.g. 3.8.1.qualifier)
- if the bundle already has a 4th part, then pad it to 2 digits (e.g.
4.1.0.01_qualifier)
- if people have requirements on specific versions, then we should
recommend that they use a limited version range. (e.g. [3.8.1, 3.8.2))

I will add this information to the wki.

orbit-dev-bounces@xxxxxxxxxxx wrote on 01/19/2007 08:44:33 AM:

>
> I agree with Pascal, making a dependency down to the qualifier does
> not make much sense.  Typically this would mean that you depend on a
> specific build of the bundle before its "final" release.  I'm not
> sure this applies to the Orbit release structure, but either way it
> should not be recommended to depend down to the qualifier of a bundle.
>
> Tom
>
>

>
> Pascal Rapicault <Pascal_Rapicault@xxxxxxxxxx>
> Sent by: orbit-dev-bounces@xxxxxxxxxxx
> 01/18/2007 04:58 PM
>
> Please respond to
> Orbit Developer discussion <orbit-dev@xxxxxxxxxxx>
>
> To
>
> Orbit Developer discussion <orbit-dev@xxxxxxxxxxx>
>
> cc
>
> orbit-dev@xxxxxxxxxxx, orbit-dev-bounces@xxxxxxxxxxx
>
> Subject
>
> Re: [orbit-dev] Bundle versions
>
>
>
>
>
> Relying on a particular version down to the qualifier is just plain
> silly. To me relying on the first 3 segments should be precise enough.
>

>
> DJ Houghton/Ottawa/IBM@IBMCA
> Sent by: orbit-dev-bounces@xxxxxxxxxxx
> 01/18/2007 04:54 PM
>
> Please respond to
> Orbit Developer discussion <orbit-dev@xxxxxxxxxxx>
>
> To
>
> orbit-dev@xxxxxxxxxxx
>
> cc
>
> Subject
>
> [orbit-dev] Bundle versions
>
>

>
>
>
>
>
>
> I recall at one point we decided that we would use a qualifier as part of
> our bundle version numbers in Orbit (although I can't seem to find that
> information right now) so we could make changes to bundles and use Update
> manager to manage the different versions.
>
> But I was thinking about it today and I remembered that we used to have
> products built on Eclipse which commonly specified an exact version match
> in their requirements because it was important for them because they knew
> that they were compatible with a specific version of a bundle.
> (org.apache.xerces comes to mind as an example)
>
> If people specify an exact version and we start using qualifiers as part
of
> our version numbers in Orbit, this could be a problem.
>
> Thoughts?
>
>
> _______________________________________________
> orbit-dev mailing list
> orbit-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/orbit-dev
> _______________________________________________
> orbit-dev mailing list
> orbit-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/orbit-dev
> _______________________________________________
> orbit-dev mailing list
> orbit-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/orbit-dev