Rule inconsistencies

this bug report is the result of the retest of Marcs bug description here: https://issues.jboss.org/browse/WINDUP-1872

I retested with two applications the permutations of source = windows and target = linux with and without cloud readiness.

I think the described problem still persists:
"While analyzing the same application (target:eap7 + cloud readiness source:windows) with or without target:linux, I had very different results."
The user right now would have to guess which combination would lead to the correct result.

• the EHCache rule is fired even though I did not specify the cloud readiness option
• some rules were not fired when source = windows was specified (such as legacy JMS, JBoss API references, Weblogics T3 protocol, etc.)
• the spring reports page is not always shown, depending on the combination.

attached is a more comprehensive report of the configuration options and results plus the used applications - the config numbers are just a reference for me.

As usual, and this is probably something you do anyways: if you find something wrong, please check if the thing being wrong can be found in other rules too