Currently, JaVers skips comparing fields of Collection type
For example, in this class, clients field is ignored:
public class Company {
private String id;
private Collection<Person> clients;
private List<Person> partners;
}
and only this warnign is logged. Expected behaviour would be using List comparator.
10:19:40.332 [main] WARN o.j.c.d.a.CollectionChangeFakeAppender - Collections: Field Collection<Person> clients; //declared in Company
are not equals but can't be compared. Raw Collection properties are not supported. Expected Set, List or any of their subclasses. JaVers uses different algorithms for comparing Sets and Lists and needs to know (statically) which one to test.
Currently, JaVers skips comparing fields of Collection type
For example, in this class,
clientsfield is ignored:and only this warnign is logged. Expected behaviour would be using List comparator.