For
bug 352081, I’m currently re-implementing/testing some of the version replacement logic in feature.xml, and I’m wondering what the use cases for the current logic are.
The current behaviour is summarized in the class DependencyArtifacts:
- 0.0.0 or null matches the latest version
- 1.2.3, i.e. without a qualifier, is equivalent to [1.2.3,1.2.4) and matches 1.2.3 with the latest qualifier.
- 1.2.3.qualifier, i.e. literal "qualifier", is equivalent to [1.2.3,1.2.4) and matches 1.2.3 with the latest qualifier.
- all other versions match artifact with that exact version, 1.2.3.foo is equivalent to [1.2.3.foo]
The cases 0.0.0, 1.2.3.qualifier, and four segment versions are clear to me – these cases occur during normal editing with the PDE UI editors.
However I don’t understand what the special handling of three segment versions is needed for? Was this PDE Build behaviour? PDE UI doesn’t seem to consider three segment versions to be a special – it shows a warning for 1.2.3 even when
there is a version [1.2.3,1.2.4) in the target platform.
@Igor: Do you remember why this was done this way? Do you have strong feelings about dropping this case?
Regards
Tobias
