Open jmle opened 4 days ago
This issue is currently awaiting triage.
If contributors determine this is a relevant issue, they will accept it by applying the triage/accepted
label and provide further guidance.
The triage/accepted
label can be added by org members.
+1
In konveyor, dependency condition versions are specified using
lowerbound
andupperbound
properties (see docs). Both bounds are included, this is, versions will be [less|greater] or equal than the number.It would be good to have a mechanism that would allow things like:
(,5.0)
[4.0, 5.0]
(4.0,)
This is quite convenient for rule authors, as there is no need to check versions in repositories. In konveyor, version numbers can only be specified with a range including the version specified. This makes the rule author have to look for the previous version number if he or she does not want to include a version up to which the rule shouldn't match (open range).