Cleanup Maven

[zorglube]

I removed some maven variable and updated version numbers.

I purpose to use mvn versions pluging or maven release plugin in order to set dependencies version or release number and building.

[rzymek]

Isn't this set during the publish process (and not updated via commit in the pom)?

[zorglube]

Yes, but it's not enough, I think.

It's set during the release process, but to be consistent into a Maven life cycle, it should evoluate into the master branch release after release.

The version change (x.x.x-SNAPSHOT -> x.x.x -> x.x+1.x-SNAPSHOT) plus tagging, commits and publishing is totally handled b the Maven Release plugin.

[ochedru]

Thank you for your PR. Actually, we got some inspiration from this article and the goal was to have an efficient CI-compatible release process, not to have an "up to date" pom.xml in git.

[zorglube]

Thank you for your PR. Actually, we got some inspiration from this article and the goal was to have an efficient CI-compatible release process, not to have an "up to date" pom.xml in git.

I understand.
I'm pretty sure it's possible have an intermediate solution that satify your requierments and the consistency into the POM.

Should I continue to work on that, or should I drop the idea ?

[ochedru]

In my opinion, this is not a critical issue. It also depends on how much time you can spend on this topic. Maybe things changed since 2016 (c.f. the date of the last article from the series)...

[zorglube]

In my opinion, this is not a critical issue. It also depends on how much time you can spend on this topic. Maybe things changed since 2016 (c.f. the date of the last article from the series)...

Okay, I'll have a look but not spend a lot of time and brain on it.

[zorglube]

It seems that GitHub has a packager Maven Release action https://github.com/qcastel/github-actions-maven-release