-
Notifications
You must be signed in to change notification settings - Fork 157
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
Incompatibility with latest version of grgit plugin #215
Comments
No, nothing in particular :) I'm glad that you created this issue beforehand. |
Associated PR #216 |
I was thinking some more about the situation where clients may want to use different versions of libraries axion is dependent upon. One possible approach would be to use shadow plugin to create axion uber jar containing relocated versions of dependencies jgit, grgit, etc. This would insulate both clients and axion from classpath pollution. Will add PR shortly. Shadow build PR #217 |
@adamdubiel The latest release 1.8.3 still does not resolve the issue when end user includes both the latest version of GrGit plugin and axion-release plugin in their project. To further illustrate, I've created a small project which demonstrates the issue. https://github.com/bigwaff/axion-blows-up The fundamental issue is axion-release depends upon a specific release version of GrGit plugin which end user can override by innocently declaring a later release version of GrGit in their project's |
Because it is such a big change, i decided to add some manual tests and literally 5 minutes age pushed a tag to some sandbox repo using snapshot version of axion-release, the one without GrGit. I feel safe to release 1.9.0 now. |
...and just released 1.9.0: https://plugins.gradle.org/plugin/pl.allegro.tech.build.axion-release |
Also checked with your sample project, works as expected:
|
Awesome. I've verified as well. |
We use latest version of grgit plugin in our builds. We like to use axion but when both the latest version grgit plugin and latest version axion plugin are both declared plugins for a project, axion has following issue performing "release" task (possibly other tasks as well).
Axion is breaking because it ends up using the latest grgit which has api changes.
I'm new to GitHub so I'm working through the process of contributing. I've forked axion-release-plugin project and updated both the jgit version and grgit versions to the latest. Everything builds and all tests pass (had to remove reference to GrgitExecption; it no longer exists). Will add PR shortly. Is there a specific contribution workflow you prefer?
The text was updated successfully, but these errors were encountered: