Issue about isComposite of variant usage

[ggunggun]

Hello,
I'm tried to upgrade the Pilot from 2025-10 to 2026-02 and found the isComposite value of variant usage is changed. Such as this SysML example:

part part0 {
	variation part part2 {
		variant part part21;
		variant ref part part22;
	}
}

The isComposite of part21 is changed from true to false.
After look through the code, seems the value of isComposite is calculated in the postProcess of UsageAdapter:

if (target.getDirection() != null || target.isEnd() || 
	// Note: A parsed Usage can only get a featuring type if it is owned via a FeatureMembership.
	!(target.eContainer() instanceof FeatureMembership)) {
	target.setIsComposite(false);
}

However, the Usage owned via VariantMembership can also have featuring type, such as the part21 and part22 in the previous SysML example.
Is this difference designed intentionally, or is truly an issue?

[seidewitz]

This is an issue. The implementation is incorrect. I will submit a bug report.

Thanks for the catch.

[seidewitz]

@ggunggun
This issue should be resolved by PR #768.