Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 366419

Summary: Rebase the resolver VersionRange impl on the new osgi VersionRange
Product: [Eclipse Project] Equinox Reporter: Thomas Watson <tjwatson>
Component: FrameworkAssignee: Thomas Watson <tjwatson>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: P3 CC: dj.houghton
Version: 3.7   
Target Milestone: Juno M5   
Hardware: PC   
OS: Mac OS X - Carbon (unsup.)   
Whiteboard:

Description Thomas Watson CLA 2011-12-12 10:15:12 EST 
The org.eclipse.osgi.service.resolver.VersionRange needs to be updated to use or probably extend the new org.osgi.framework.VersionRange class to fully support pre-release versions.
Comment 1 DJ Houghton CLA 2011-12-12 10:18:58 EST 
Is there anything consumers should do here? Are we going to recommend as best practice that people refer to the framework's VersionRange class explicitly or not worry about it since they're compatible anyway?
Comment 2 Thomas Watson CLA 2011-12-12 14:18:36 EST 
(In reply to comment #1)
> Is there anything consumers should do here? Are we going to recommend as best
> practice that people refer to the framework's VersionRange class explicitly or
> not worry about it since they're compatible anyway?

I intend to make them fully compatible.  Folks already referring to the org.eclipse.osgi.service.resolver.VersionRange should continue to do so since that is the type that is returned by the various types in org.eclipse.osgi.service.resolver.  To have clients start referring to the org.osgi.framework.VersionRange when dealing with the org.eclipse.osgi.service.resolver package would start looking rather messy and will not really gain them much.