Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

AssertJ upgrade policy #183

Open
nathankooij opened this issue Jun 22, 2021 · 1 comment
Open

AssertJ upgrade policy #183

nathankooij opened this issue Jun 22, 2021 · 1 comment

Comments

@nathankooij
Copy link

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.

@starksm64
Copy link
Contributor

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants