The component descriptor may contain a <Requires> <SystemRelease>X.Y.Z</SystemRelease> </Requires> where Note:
The version numbers refer to the Isight
release, not your component.
Version numbers can be specified as a wildcard “ <Requires> <SystemRelease>3.*.*</SystemRelease> </Requires> indicates that the component can be loaded into any 3.
<Requires>
<SystemRelease>2024.*</SystemRelease>
</Requires>
indicates that the component can be used only in the 2024 release of Isight (any fix level). Such a component cannot be used in version 5.0 or 5.x. Note:
Both of the prior examples would prevent the loading
of the component into future major versions of the system (e.g., Isight
2024).
A plus sign “
+ ” can be appended to the specification
to indicate that all versions later than the specification are also allowed.For example: <Requires> <SystemRelease>5.0.1+</SystemRelease> </Requires> would allow the component to run in any version of Isight
equal to or later than version 2024.
This would include any version 5.0 fix level, version 5.5, etc. This
format is recommended when a component depends on a specific new feature
of the infrastructure. The specification should name the version of the
infrastructure that introduced the new feature, with the “ If the component descriptor does not contain a required version tag,
the default is “ |