Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 315108 - [metadata] Version Type independent semantics for range generation
Summary: [metadata] Version Type independent semantics for range generation
Status: CLOSED WONTFIX
Alias: None
Product: Equinox
Classification: Eclipse Project
Component: p2 (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: P2 Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2010-05-31 12:11 EDT by Thomas Hallgren CLA
Modified: 2019-11-14 03:14 EST (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Thomas Hallgren CLA 2010-05-31 12:11:57 EDT
We need some version type independent way to create ranges that correspond to various compatibility strategies.

Example:
You have an OSGi version "1.2.3.abc" and you want to create ranges that includes versions that are related. Today, we have the well known "perfect, equivalent, compatible, greaterOrEqual" rules for this.

 Perfect: "[1.2.3.abc,1.2.3.abc]"
 Equivalent: "[1.2.0,1.3.0)"
 Compatible: "[1.0.0,2.0.0)"
 GreaterOrEqual: "1.2.3.abc"

In addition to those we might want to consider:

 Unqualified: "[1.2.3,1.2.4)"

Another very useful range is a combination where the lower bound is equivalent and the upper bound is compatible, i.e. "[1.2.0,2.0.0)". Not sure what to call that. Suggestions welcome.

So first task is to identify the set of ranges that are needed. The second task is how to describe this in a version type independent way so that the given semantics can work for different types of versions.
Comment 1 Lars Vogel CLA 2019-11-14 03:14:31 EST
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

If the bug is still relevant, please remove the "stalebug" whiteboard tag.