This is a general design note, perhaps for a 2.0.0 release since it breaks backwards compatibility: I would suggest maybe to reorganize the org.passay package into separate sub-packages - one for rules, one for character data/sequences, one for message handling, one for core data objects (password data, references, etc.), one for utilities etc. or some other division that makes sense. The current mix of all classes in one package (except dictionary classes which do have their own subpackage) makes it a bit harder to work with and to clearly see the project design and structure.
This is a general design note, perhaps for a 2.0.0 release since it breaks backwards compatibility: I would suggest maybe to reorganize the org.passay package into separate sub-packages - one for rules, one for character data/sequences, one for message handling, one for core data objects (password data, references, etc.), one for utilities etc. or some other division that makes sense. The current mix of all classes in one package (except dictionary classes which do have their own subpackage) makes it a bit harder to work with and to clearly see the project design and structure.