Skip to content

Conversation

@henryx
Copy link
Collaborator

@henryx henryx commented Nov 3, 2025

With this PR we switch from Gradle to Maven. Reasons are two:

  • Version of Gradle used is too old. THis doesn't permit to upgrade to new Java versions.
  • Upgrade of Gradle isn't direct possible, because build.gradle has too deprecated statements.

So, to resolve the problem, I've decided to switch to Maven. To do this, I've restructured tests and I've written a pom.xml that permit to switch without problems. I've also adapted the Github action's CI to use Maven instead of Gradle

@vbabenkoru
Copy link

Would you consider keeping Gradle? I can try updating the Gradle version and fixing the deprecated stuff

@henryx
Copy link
Collaborator Author

henryx commented Nov 4, 2025

@vbabenkoru thank you for the offer, but this is the second time I've neglected build.gradle maintenance and this create problems to the evolution of the library. At this point, I prefer to switch to Maven, which is more stable (pom.xml had few deprecations in his history) and this permit me to have a simple management of the project

@henryx henryx merged commit c920bae into jopenlibs:master Nov 9, 2025
17 checks passed
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