You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We were wondering what your policy regarding AssertJ upgrades is as the current version is (indirectly) blocking us from upgrading AssertJ in our internal projects.
To give some more background, in our internal projects we use ConstraintViolationAssert from hibernate-validator. Since the version of hibernate-validator must be in sync with the TCK, they have fixed AssertJ to 3.8.0. Unfortunately, version 3.20.x of AssertJ broke compatibility with 3.8.0 in regards how they use it within Hibernate. As such, we cannot upgrade our AssertJ version either.
I can also provide an upgrade PR if that's helpful.
The text was updated successfully, but these errors were encountered:
So the transitive dependency of hibernate-validator on assertj is causing a problem in your build? I see this should be a test scoped dependency but currently it is not in hibernate-validator. Can you just exclude that transitive dependency in your dependency on hibernate-validator?
We were wondering what your policy regarding AssertJ upgrades is as the current version is (indirectly) blocking us from upgrading AssertJ in our internal projects.
To give some more background, in our internal projects we use
ConstraintViolationAssert
fromhibernate-validator
. Since the version ofhibernate-validator
must be in sync with the TCK, they have fixed AssertJ to 3.8.0. Unfortunately, version 3.20.x of AssertJ broke compatibility with 3.8.0 in regards how they use it within Hibernate. As such, we cannot upgrade our AssertJ version either.I can also provide an upgrade PR if that's helpful.
The text was updated successfully, but these errors were encountered: