-
Notifications
You must be signed in to change notification settings - Fork 160
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
SnapshotDependenciesChecker fails for multi module project #330
Comments
Same here. All project() dependencies are breaking release. |
@Kindrat is your change actually releasing I have similar issue but instead of ignoring |
@dlesniakdev yeah, that was for snapshot release. All external deps are releases, while internal modules are snapshots. |
We have an internal plugin that we include Axion with and also encountered this issue when updating; Downgrading Axion to
It appears its most likely related to changes that occurred with; 7202376 But I'm not sure how we opt-out of this behavior and should have probably been opt-in instead of changing the existing default behavior |
Hello, I am facing the same issue SnapshotDependenciesChecker fails for multi module project. |
@mazdack @radusuma @k3mist could you test @Kindrat's PR https://github.com/allegro/axion-release-plugin/pull/331/files? |
We could marge it in next release if it helps with your issues! |
I just ran into this, but only due to upgrading to gradle 7.6. On gradle 7.5.1 I did not have this problem. Edit: Turns out my problems stemmed from having the plugin on each submodule when I really wanted it only on the root project. |
merged and released! |
For example you have 2 modules: api and server.
Server uses api module like this
implementation(project(":api"))
Then the snapshot check fails:
> The project uses snapshot versions - can't release. Snapshots found
I think there should be possibility to ignore some dependencies.
The text was updated successfully, but these errors were encountered: