Switch to use implementation config

- Now switching to use implementation configuration as it
  works better with aot tooling.
- Relates #470
This commit is contained in:
Janne Valkealahti
2022-09-06 19:39:14 +01:00
parent cf7c409d1c
commit a9a420df22
2 changed files with 1 additions and 11 deletions

View File

@@ -46,10 +46,7 @@ public class ManagementConfigurationPlugin implements Plugin<Project> {
management.setCanBeResolved(false);
PluginContainer plugins = project.getPlugins();
plugins.withType(JavaPlugin.class, (javaPlugin) -> {
configurations.getByName(JavaPlugin.COMPILE_CLASSPATH_CONFIGURATION_NAME).extendsFrom(management);
configurations.getByName(JavaPlugin.RUNTIME_CLASSPATH_CONFIGURATION_NAME).extendsFrom(management);
configurations.getByName(JavaPlugin.TEST_COMPILE_CLASSPATH_CONFIGURATION_NAME).extendsFrom(management);
configurations.getByName(JavaPlugin.TEST_RUNTIME_CLASSPATH_CONFIGURATION_NAME).extendsFrom(management);
configurations.getByName(JavaPlugin.IMPLEMENTATION_CONFIGURATION_NAME).extendsFrom(management);
});
plugins.withType(JavaTestFixturesPlugin.class, (javaTestFixturesPlugin) -> {
configurations.getByName("testFixturesCompileClasspath").extendsFrom(management);

View File

@@ -21,10 +21,3 @@ graalvmNative {
version = "0.1.1"
}
}
// TODO: workaround until boot's aot plugin automatically extends
// from all super configurations like graalvm's plugin does.
configurations {
aotCompileClasspath.extendsFrom management
aotRuntimeClasspath.extendsFrom management
}