Re: [orbit-dev] Bundle versions

[Pascal Rapicault <Pascal_Rapicault@xxxxxxxxxx>]

There is no java code development going
on there, however the manifest file can be considered as being developed
and nothing says that we won't need to make change to it (for example use
new osgi headers, refine what is exported, buddy loading markup, ...).
This is why we need a qualifier.

Eugene Kuleshov <eu@xxxxxxxx>
Sent by: orbit-dev-bounces@xxxxxxxxxxx

01/18/2007 05:05 PM

Please respond to
Orbit Developer discussion <orbit-dev@xxxxxxxxxxx>

To	Orbit Developer discussion <orbit-dev@xxxxxxxxxxx>
cc
Subject	Re: [orbit-dev] Bundle versions

  I still don't understand this. Orbit project does not assume any
development, so there is no code or API evolution and released bundles
won't need to have any version changes and actually should match the 
version of the the bundled component/jar. So, all in all qualifiers 
don't really make sense.

  regards,
  Eugene


DJ Houghton wrote:
> 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