This is an incremental update to the 2026-02 release. It corresponds to Eclipse plugin version 0.58.0.
Language Features
None.
Model Libraries
None.
Backward Incompatibilities
- Filter expressions. Many examples of feature references in filter expressions currently use a qualified name notation, such as
However, the
filter @Annotations::ApprovalAnnotation and Annotations::ApprovalAnnotation::approved and Annotations::ApprovalAnnotation::level > 1;checkConnectorTypeFeaturingconstraint is impossible to satisfy for the binding connectors implied by these feature references. The Pilot Implementation was not reporting this as an error, which was not conformant with the normative metamodel for KerML (and, so, SysML, too). Now that this nonconformity has been corrected, the above feature references will cause "Must be accessible feature" errors. To avoid such errors, the qualified names need to be changed to feature chains such as in the following:[PR #743]filter @Annotations::ApprovalAnnotation and (as Annotations::ApprovalAnnotation).approved and (as Annotations::ApprovalAnnotation).level > 1;
Issue Resolutions
This release proactively implements the resolution to the following issue, which the KerML 1.1 RTF has elevated to be a "blocker" issue.
- KERML11-191 Problem with deriveTypeFeatureMembership
[PR #749]
Jupyter
None.
Visualization (PlantUML)
None.
Technical Updates
None.
Bug Fixes
- Filter expressions. Removed code that suppressed violations of
checkConnectorTypeFeaturingwithin feature references in filter expressions.
[PR #743] - Semantic metadata. Fixed a bug that could cause an incorrect name resolution when using semantic metadata.
[PR #744] - Adapters. Fixed bugs in
TypeAdapterandAssignmentUsageAdapter.
[PR #747] - Derived property. Corrected the derivation computation for the property
Feature::crossFeatureso it takes impliedCrossSubsettinginto account.
[PR #748]