Details
-
New Feature
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
-
None
-
None
Description
Many things are pluggable in Ivy, but something is still not flexible enough: definition of dynamic revisions. Actually only two things are possible in this area:
- latest.integration, which takes the latest version, wihtout any filtering
- latest subversion, noted prefix+, which takes the latest among revisions matching the given prefix
Having the possibilities to define version range would be good, but what could be even more powerful is to be able to provide custom dynamic version matcher.
The matcher would be able to filter out revisions at two times: with the revision only (as a string), and with the parsed module descriptor (to filter out modules based on status, for example). Since parsing module descriptors can be very time consuming, the version matcher should tell if it needs it or not.
This would allow easy implementation of latest.release and latest.milestone feature, requested in IVY-47