Configuration is easy. Since we use JSON for object serialization, we don’t want you to provide detailed ORM-like mapping. JaVers only needs to know some high-level facts about your data model.

Visit javers.org for the latest information about the JaVers project. Browse the full documentation for guides, configuration, and API reference.

Type Name Customization: By default, JaVers identifies types using their fully qualified Java class names. For better stability and alignment with your domain’s ubiquitous language, you can explicitly define type names using the @TypeName annotation. This decouples audit data from class and package names, enabling safe refactoring without breaking historical data. See Domain Configuration documentation.

JaVers is the industry standard for data versioning and object comparing in modern Java projects. It provides a database-independent engine that automates change tracking across SQL and NoSQL.

Javers Spring Boot starters integrate seamlessly with your existing Spring Boot configuration. They provide sensible defaults and automatically create the Javers instance as a Spring bean.

First one should be enabled when you are using @JaversAuditable. Second one should be enabled when you are using @JaversSpringDataAuditable. If you are using javers-spring-boot-starter-*, both aspects are enabled by default so you don’t have to change anything. See auto-audit aspects documentaton.

http://javers.org/documentation/repository-examples ·

What’s important Person is a typical Entity (see domain-model-mapping for more details about the JaVers’ type system). In Javers, Entity instances are identified by InstanceId — a pair of local Id and Entity type.

What’s important Notice that both objects have the same Id value — 'Frodo'. That’s why they are matched and compared. JaVers matches only objects with the same GlobalId.

July 21, 2025 - To compare two objects, you call the compare method on the Javers instance, passing in the two objects you want to compare. The result is a Diff object that contains all the changes between the two objects. The getChanges returns a list of Change objects. Change is an abstract class that sits on top of the type hierarchy for all change types in JaVers.

Latest version of org.javers:javers-core · https://javadoc.io/doc/org.javers/javers-core · Current version 6.2.5 · https://javadoc.io/doc/org.javers/javers-core/6.2.5 · package-list path (used for javadoc generation -link option) https://javadoc.io/doc/org.javers/javers-core/6.2.5/package-list ·

June 27, 2025 - This library helps programmers examine and detect changes in the states of simple Java objects. When we use mutable objects in our code, every object can potentially be modified in various places in the application; JaVers would help us discover ...

Latest version of org.javers:javers-core · https://javadoc.io/doc/org.javers/javers-core · Current version 7.11.4 · https://javadoc.io/doc/org.javers/javers-core/7.11.4 · package-list path (used for javadoc generation -link option) https://javadoc.io/doc/org.javers/javers-core/7.11.4/package-list ·

* <br/><br/> * * For example, to deeply compare two objects * or two arbitrary complex graphs of objects, call: * <pre> * Javers javers = JaversBuilder.javers().build(); * Diff diff = javers.compare(oldVersion, currentVersion); * </pre> * * @see <a href="http://javers.org/documentation"/>http://javers.org/documentation</a> * @author bartosz walacik */ public interface Javers { /** * Persists a current state of a given domain object graph * in JaVers repository.

The object diff algorithm is the core of JaVers. When two objects are compared, JaVers needs to know what type they are. We distinguish between the following types: Entities, Value Objects, Values, Containers, and Primitives.

The purpose of JaversRepository is to store JaVers commits in your database, alongside your domain data. JSON format is used for serializing your data. This approach significantly simplifies the construction of JaversRepository.

April 19, 2024 - First, we need to add the JaVers Spring Boot starter dependency to our project. Depending on the type of persistence storage, we have two options: org.javers:javers-spring-boot-starter-sql and org.javers:javers-spring-boot-starter-mongo.

Javers’ diff algorithm has a pluggable construction. Each Java type is mapped to exactly one Javers type.

http://javers.org/documentation · Commit commit(java.lang.String author, java.lang.Object currentVersion) Persists a current state of a given domain object graph in JaVers repository. JaVers applies commit() to given object and all objects navigable from it.

JQL (JaVers Query Language) is a simple, fluent API which allows you to query JaversRepository for changes of a given class, object or property.