-
Notifications
You must be signed in to change notification settings - Fork 271
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
Transitive dependencies of a intellijPlatformPluginModule are lost #1655
Comments
@abrooksv could you please verify it once again with |
Yes, it is still broken |
I have just verified that on my local, and it seems to be working just fine. The folowing is required to be present in the root module: dependencies {
intellijPlatform {
implementation(project(":module")) {
pluginModule(this)
}
}
} The With that, the |
I hacked your test to show it being broken, seems to only be in certain usage configuration:
TL;DR:
Notice that dummy-0.1.2.jar is missing |
It's expected to be broken as you're not supposed to use it alone without |
Can I go hide in shame now? |
The And please don't worry about that — this is new and confusing. The documentation still doesn't cover that scenario - that'll be properly described next week. |
Ok, I think we can close this then |
What happened?
Using
intellijPlatformPluginModule
on a module that brings in 3rd party libs causes the lips to be lost when building the final zipRelevant log output or stack trace
No response
Steps to reproduce
intellijPlatformPluginModule(project(":moduleA"))
:buildPlugin
, see Zip contain the merged moduleA's jar into the composedJar, but the zip is missing the commonmark jar as a sibling jar (since composeJar isn't supposed to do any shadowing on 3rd party libs)Doing the following works-ish by bringing in the transitive deps:
but it composes the jar from
moduleA
and includes themoduleA-base.jar
into the Zip which seems incorrect as wellGradle IntelliJ Plugin version
2.0.0-beta7
Gradle version
8.8
Operating System
None
Link to build, i.e. failing GitHub Action job
No response
The text was updated successfully, but these errors were encountered: