WhiteList and BlackList incompatibility

[isaaclo97]

Is your feature request related to a problem? Please describe.
If you want to declare several blacklists and whitelists, mork does not know which one to select. There should be a mechanism where the user can decide without having to comment or delete the class.

Describe the solution you'd like
Allow the user as a parameter to decide which one to use for autoconfiguration.
It can be using --whitelist (in case you have only one class you would select the one in the whitelist) or --whitelist Java.class (in case there are several, select the class) or --blacklist.
Both would not be allowed to appear and with this the user can decide which one to use.

[rmartinsanta]

Currently, only either a whitelist or a blacklist are allowed, as the implementation is detected and chosen automatically. I agree that implementing a new parameter would give more flexibility and remove the need to comment or otherwise disable existing blacklists or whitelists. However, this should be implemented in a way that the current behavior is preserved: if there is only a whitelist or a blacklist available, it should be used by default without requiring any parameter.

I think this is a good first issue as the number of modifications required to implement it should be low, and unless people show interest in this feature it is not a priority.