You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Gradle's api & compileOnlyApi configurations created by its java-library plugin do not work, and transitive implementation scope dependencies get exposed, when this plugin is used
#1799
Gradle's java-library plugin is more suitable for IntelliJ plugin development than regular java. I think it must be supported, since it a basic Gradle feature.
See:
If you look carefully at the output on the screenshot below, you will see that org.apache.commons:commons-lang3:3.5 was exposed as a transitive dependency though implementation dependency scope, which is not supposed to happen. It is bad.
The setup:
build.gradle.kts
plugins {
`java-library`
//id("org.jetbrains.kotlin.jvm") version "2.0.20"
id("org.jetbrains.intellij.platform") version "2.1.0"
}
dependencies {
implementation(project(":subpr"))
}
repositories {
mavenLocal()
mavenCentral()
}
### Steps to reproduce
In the description.
### Gradle IntelliJ Plugin version
2.1.0
### Gradle version
8.10.2
### Operating System
Linux
### Link to build, i.e. failing GitHub Action job
_No response_
The text was updated successfully, but these errors were encountered:
AlexanderBartash
changed the title
Gradle's api & compileOnlyApi configurations created by its java-library plugin do not work, when this plugin is used
Gradle's api & compileOnlyApi configurations created by its java-library plugin do not work, and transitive implementation scope dependencies get exposed, when this plugin is used
Oct 16, 2024
AlexanderBartash
added a commit
to AlexanderBartash/intellij-platform-gradle-plugin
that referenced
this issue
Oct 16, 2024
…arApi (extends api & compileOnlyApi) configuration with JAVA_API usage attribute value. Also replaced java plugin by java-library plugin, because it is a more proper plugin for IntelliJ plugin projects (they are libraries).
…arApi (extends api & compileOnlyApi) configuration with JAVA_API usage attribute value. Also replaced java plugin by java-library plugin, because it is a more proper plugin for IntelliJ plugin projects (they are libraries).
AlexanderBartash
added a commit
to AlexanderBartash/intellij-platform-gradle-plugin
that referenced
this issue
Oct 21, 2024
…arApi (extends api & compileOnlyApi) configuration with JAVA_API usage attribute value. Also replaced java plugin by java-library plugin, because it is a more proper plugin for IntelliJ plugin projects (they are libraries).
AlexanderBartash
added a commit
to AlexanderBartash/intellij-platform-gradle-plugin
that referenced
this issue
Oct 22, 2024
…arApi (extends api & compileOnlyApi) configuration with JAVA_API usage attribute value. Also replaced java plugin by java-library plugin, because it is a more proper plugin for IntelliJ plugin projects (they are libraries).
What happened?
Gradle's
java-library
plugin is more suitable for IntelliJ plugin development than regularjava
. I think it must be supported, since it a basic Gradle feature.See:
Sub-issue:
org.apache.commons:commons-lang3:3.5
was exposed as a transitive dependency thoughimplementation
dependency scope, which is not supposed to happen. It is bad.The setup:
build.gradle.kts
settings.gradle.kts
subpr/build.gradle.kts
Expected result:
org.jetbrains:annotations:26.0.1
is available to the root project transitively from the sub project.Actual result result:
org.apache.commons:commons-lang3:3.5
) is there.If kotlin plugin is added to the sub-project, somehow it starts working, but implementation is still exposed:
Relevant log output or stack trace
The text was updated successfully, but these errors were encountered: