-
Notifications
You must be signed in to change notification settings - Fork 278
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
2.4.0 Is bringing some different dependencies in the class path and cause the build to fail #1906
Comments
We have the same problem, noticed it when running in combination with Sonar. However it only seems to happen when the OS is Linux? Here's the log: |
Given that two different Gradle plugins require a dependency in two different versions in a single build classpath, I'm not entirely sure how to correctly address that. |
So the first thing would be to find out where the broken class is coming from because when I list the plugin dependency versions everything is fine:
Both plugins use the lastest version
Update: I think I found the problem. Something is seriously wrong with how the The original class from
However
The problem is likely not just |
Fun Fact: The same problem seems to be present since I highly recommend that you do not shade these dependencies into the jar and if you do so use a dedicated package so that they don't overlap with the actual dependencies. |
Thank you for the investigation, @AB-xdev! The current state of the IntelliJ Platform Gradle Plugin is that I have the JPS Model transitive dependencies present in place, which come from the Plugin Verifier's structure libraries. Unfortunately, they're available only in the custom non-MavenCentral repositories, and it's not possible for users using this Gradle plugin to add required repositories to their setup. Bundling them is required for now, but eventually, PV should get rid of them (or at least publish all required pieces to MavenCentral). ![]() |
What happened?
Hi
I have created this repo in which the issue is reproducible.
Basically with 2.3.0 things work and with 2.4.0 I am getting:
after a short investigation, I saw that the plugin structure is bringing a different Apache-commons-compress dependency, and it caused the error since another plugin expects the public one. The versions are the same, but the dependencies are not:
Relevant log output or stack trace
Steps to reproduce
Run this repo:
https://github.com/Jonatha1983/240-dependencies-bug
Gradle IntelliJ Plugin version
2.4.0
Gradle version
8.13
Operating System
None
Link to build, i.e. failing GitHub Action job
https://github.com/Jonatha1983/240-dependencies-bug
The text was updated successfully, but these errors were encountered: