Skip to content

Variability: Changing feature model constraint should cause a adapt-to-FM-error in configurations #1844

Description

@kbirken

When changing a constraint (or adding/removing some constraint) in a feature model, its configurations currently are not marked with There were changes in the Feature Model. Please adapt this config to its Feature Model. (see check_FeatureModelConfiguration checking rule). This is wrong, as it might change the automatic setting of selection states and values in the configuration. So these changes should be incorporated in the hashcode compared in FeatureModelConfiguration.shouldAdaptToFM().

Implementation note: We are not allowed to just change the computation of the hashcode, as it would induce the above error on all configurations in any user models. Thus, a mechanism has to be put in place to be backwards compatible here. We had this problem before, we should investigate how we solved it the last time.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No fields configured for Bug.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions