Fork me on GitHub

Backward compatibility: (v3.3)

1) Versioning & backward compatibility

Since version 2, the pac4j project has adopted the semver versioning, to make things clearer.

Given a version X.Y.Z:

Generally, pac4j implementations will adopt the semver versioning when upgrading to pac4j version 2, if they don’t already have.

Notice that, while pac4j-* modules are backward compatible, you should always add the pac4j-core dependency in the same version as the upgraded pac4j-* dependency.

2) Maintenance

Two stable and released streams of pac4j are maintained at the same time.

During the development of the version 2, the streams: 1.8 and 1.9 are maintained.

After the release of the version 2, the streams: 1.9 and 2.x will be maintained.

After the release of the version 3, the streams: 2.x and 3.x will be maintained.

And so on.