Overview (Gradle Java Projects)

Gradle Java Projects
Package	Description
org.netbeans.modules.gradle.java.api
org.netbeans.modules.gradle.java.api.output
org.netbeans.modules.gradle.java.spi.debug
org.netbeans.modules.gradle.java.spi.support

GradleJavaProjectAPI
The Gradle Java Project API provides some miscellaneous friend APIs and SPIs relating to Gradle Java projects.

What is New (see all changes)?

Jan 4 '24 Support for per-language output directories

Gradle 6.7 introduced Java Toolchains to separate Gradle Java Runtime and the Java used for compilation (and other Java execution). GradleJavaSourceSet.getCompilerJavaHome has been added to return the Java Home of the JDK in use for compilation.

In addition JavaToolchainSsupport is provided in order to be easily work with the JDK home directories.
Jun 28 '22 Support for per-language output directories
Each language plugin typically generates output to a specific directory. The mapping allows more precise output-to-source mapping.
Feb 18 '22 Location can represent nested classes
Location is now capabe to represent java code location inside nested classes as well.
Apr 10 '21 Deprecating Gradle 7.0 removed API-s
GradleJavaSourceSet methods getCompileConfigurationName() and getRuntimeConfigurationName() were deprecated as Gradle 7.0 does no longer supports them. They return null on Gradle 7.0.
Mar 27 '21 Support for explicit commandline arguments
Gradle Java interpolate javaExec.jvmArgs and javaExec.args tokens in action mapping that can be used to pass explicit JVM and application parameters to user process started by Gradle build. For more details, see ProjectActions.TOKEN_JAVAEXEC_JVMARGS

Use Cases

API/SPI to be used by modules wanting to enhance the Gradle Java project's integration in the IDE.

Exported Interfaces

This table lists all of the module exported APIs with defined stability classifications. It is generated based on answers to questions about the architecture of the module. Read them all...

Group of java interfaces

Interface Name

In/Out

Stability

Specified in What Document?

GradleJavaProjectAPI

Exported

Under Development

The Gradle Java Project API provides some miscellaneous friend APIs and SPIs relating to Gradle Java projects.

Group of property interfaces

Interface Name	In/Out	Stability	Specified in What Document?
javaExec.jvmArgs	Exported	Stable	`${javaExec.jvmArgs}` token is replaced in action mappings for JVM arguments collected from ExplicitProcessParameters in action's context Lookup. See ProjectActions.TOKEN_JAVAEXEC_JVMARGS for more details.
javaExec.args	Exported	Stable	`${javaExec.args}` token is replaced in action mappings for application parameters collected from ExplicitProcessParameters in action's context Lookup. See ProjectActions.TOKEN_JAVAEXEC_ARGS for more details.
javaExec.runWorkingDir	Exported	Stable	`${javaExec.runWorkingDir}` token is replaced in action mappings with working directory retrieved from ExplicitProcessParameters in action's context Lookup. See ProjectActions.TOKEN_JAVAEXEC_CWD for more details.
javaExec.runEnvironment	Exported	Stable	`${javaExec.runEnvironment}` token is replaced in action mappings with environment variables retrieved from ExplicitProcessParameters in action's context Lookup. See ProjectActions.TOKEN_JAVAEXEC_ENV for more details.

Group of lookup interfaces

Interface Name

In/Out

Stability

Specified in What Document?

GradleJavaDebugger

Exported

Private

This module provides a lookup implementation for GradleJavaDebugger which makes it easy to attach a configured Java debugger to a running process.

Implementation Details

Where are the sources for the module?

The sources for the module are in the Apache Git repositories or in the GitHub repositories.

What do other modules need to do to declare a dependency on this one, in addition to or instead of a plain module dependency?

XXX no answer for deploy-dependencies

Read more about the implementation in the answers to architecture questions.

Gradle Java ProjectsUnder Development