You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Java compiler used to build the FeatureIDE plugin: N/A
Issue description
When saving (probably when loading directly) dimacs files to xml, FEatureIDE ignores features that do no appear in constraints.
The dimacs parser should use all the features defined in the first rows befor the "p cnf x y" entry, they are meant to be optional.
As shown below, the dimacs file declares 6 features, but the xml has only 4, the 4 that appear in constraints.
The dimacs file I used:
c 1 base
c 2 weight
c 3 empty
c 4 executivefloor
c 5 twothirdsfull
c 6 overloaded
p cnf 6 3
-6 2 0
-5 2 0
1 0
The text was updated successfully, but these errors were encountered:
meinicke
changed the title
Saving dimacs to xml invalid
Saving dimacs to xml deletes features
Mar 7, 2019
meinicke
changed the title
Saving dimacs to xml deletes features
Saving dimacs to xml ignores features declared in comments
Mar 8, 2019
tthuem
changed the title
Saving dimacs to xml ignores features declared in comments
Saving dimacs to xml ignores features not occurring in constraints
Mar 11, 2019
Fixed null pointer for constraint dialog.
Fixed potential null pointer for getting analysis results for specific
features or constraints.
Fixed problem with FeatureIDE context menu.
Fixed#868.
Fixed#869.
Prerequisitives
Issue description
When saving (probably when loading directly) dimacs files to xml, FEatureIDE ignores features that do no appear in constraints.
The dimacs parser should use all the features defined in the first rows befor the "p cnf x y" entry, they are meant to be optional.
As shown below, the dimacs file declares 6 features, but the xml has only 4, the 4 that appear in constraints.
The dimacs file I used:
c 1 base
c 2 weight
c 3 empty
c 4 executivefloor
c 5 twothirdsfull
c 6 overloaded
p cnf 6 3
-6 2 0
-5 2 0
1 0
The text was updated successfully, but these errors were encountered: