It is possible to install a subsystem via incomplete file name location. This allows deploying subsystems with build version suffix and installing them only by the name.
Using Auto-completion
Auto-completion feature can be used when installing subsystems in one of the ways via:
Subsystem API – Subsystem#install(String location)
Subsystem BOOT file
The provided location parameter must point to one of the following:
a complete file name, which is already supported;
an incomplete file name, which is added with this feature, on the local file system.
File location can be either an absolute or a relative path. It must point to the exact folder, containing the subsystem file.
As a result:
Only the folder referred in location parameter will be scanned for a matching subsystem.
File names that have this parameter, or its file name part as a prefix, will be considered.
Among all files that match this prefix, the one with lexicographically smallest name will be chosen.
Example
Consider the following directory structure, containing subsystem archives:
foo/
foo/bar/a.esa
foo/bar/ab.esa
foo/bar/bc.esa
Installing with location foo/bar/a will install subsystem from file a.esa, since it is the closest match and lexicographically smallest.
Installing with location foo/bar/ab will install subsystem ab.esa.
Installing with location foo/ab.esa or foo/bar/abc will throw an error, since there is no matching file name by prefix, located in the referred folder.
