Community
Participate
Working Groups
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.
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?
(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.
Fix released with commit: http://git.eclipse.org/c/equinox/rt.equinox.framework.git/commit/?id=edf4ec0bb31613957e9110955b509620a5321375