-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Comments
Conversation
Overview
Try out AssertJ 4.0 prior to its release.
I hereby agree to the terms of the JUnit Contributor License Agreement.
Definition of Done
- There are no TODOs left in the code
- Method preconditions are checked and documented in the method's Javadoc
- Coding conventions (e.g. for logging) have been followed
- Change is covered by automated tests including corner cases, errors, and exception handling
- Public API has Javadoc and
@APIannotations - Change is documented in the User Guide and Release Notes
gradle/libs.versions.toml
Outdated
| asciidoctorj-pdf = "2.3.19" | ||
| asciidoctor-plugins = "4.0.4" # Check if workaround in documentation.gradle.kts can be removed when upgrading | ||
| assertj = "3.27.3" | ||
| assertj = "4.0.0-M1" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We now publish snapshots:
| assertj = "4.0.0-M1" | |
| assertj = "4.0.0-SNAPSHOT" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks! You don't publish snapshot Javadoc anywhere, do you?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If I'm not mistaken, the Javadoc JAR also gets generated and published to Maven Central, but I don't know how its content could be consumed/linked.
As part of version 4 work, I plan to publish the Javadoc also to our own domain to relax a bit the dependency to javadoc.io, and the new publishing will also include snapshot content.
25a3aa0 to
8911274
Compare
|
Looks like xmlunit needs to be adjusted due to assertj/assertj@989faf8 |
Thanks for the heads up! We'll reach out to the project about it. |