Skip to content

Conversation

@ancho
Copy link
Member

@ancho ancho commented Nov 21, 2025

This may break things.

It started with "Come on....let's update the asciidoctorj dependency to the latest and greatest. How hard could it be."
Well that escalated quickly and now all dependencies (except orientdb) are as far as i could push them.

Maybe I went a little bit to far upgrading to gradle 9.2.0, removing most of the deprecation warnings and get rid of some older plugins. With the side effect of lifting the source and code compatibility to jdk 11 at least.

But here we are now. I hope most of the stuff is still working and the coverage of the tests are not to bad.

@ancho ancho force-pushed the feature/update-asciidoctorj branch from c1a47a0 to 06c59b0 Compare November 22, 2025 20:49
@ancho ancho force-pushed the feature/update-asciidoctorj branch from 06c59b0 to d56206e Compare November 23, 2025 09:44
get rid of modification problems that hinder windows tests to delete the temporary junit directory
@ancho
Copy link
Member Author

ancho commented Nov 24, 2025

Ok. I think this should really be it.
After the failing windows pipeline I split the broken test into os specific tests, as the filesystem behaviour is a little bit different.
Then I removed the junit 4 dependencies. Because......I mean.....it had to be done. There is no good reason not to migrate forward. ( I would have pushed it to junit 6 but that needs minimum compatibility of jdk17. I bit my tongue and postponed it because it is not relevant for the dependency updates currently)

I think it is ready to merge now but a few pairs of eyes and some tests from someone else would be great.

@jonbullock jonbullock added this to the v2.8.0 milestone Dec 30, 2025
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

Successfully merging this pull request may close these issues.

2 participants