Today I released version 1.1.1.
Main reason for this release is this bugfix:
Decisiontable.getRulesNotDisjunct() did not report - as expected the first two rules which are not unique (if such rules were found by Decisiontable.checkRulesForBeingDisjunct() - but the first two rules being disjunct! Was were no testcases to cover this usecase? - Of course there was (and still are)! But this bug would not discovered by this testcases because they was wrong. The author apologize for any inconvienance! This happened around inverting the meaning of the flag which is handled by Rule.getDisjunctCheckFailed() / Rule.setDisjunctCheckFailed(). The author apologizes for any inconvenience.
Approving that all rules are disjunct / detect if there are rules which are not disjunct still works in all versions! I checked for version 1.1 and 1.0 does not have the fixed feature.
Thus the Version 1.1 was removed from download. The problem des not appear in Version 1.0 because this version lacks the fixed feature so this version is still available for download.
This bugfix will by take effect JDecisiontable from version 1.1-PRE4 which uses this library in version 1.1.1. Until then, JDecisiontable will suggest obviously wrong rules to begin the search for non-disjunct rules with.