kevin macksamie <> in Gradle

Remove application plugin from misbehaving plugins

The application plugin now creates and references tasks lazily. As such,

the plugin can be removed from the list of misbehaving plugins in


Signed-off-by: Kevin Macksamie <>

Use lazy task API in the application plugin

Signed-off-by: Kevin Macksamie <>

Exclude application plugin from behaved plugins

With the ApplicationPluginIntegrationTest inheriting the tests from

WellBehavedPluginTest, it fails the "does not realize all possible

tasks" test. In order to make the test pass, the application plugin must

be included in the list of misbehaving plugins inside that test. This

confirms that the application plugin in its current state is not lazy.

Signed-off-by: Kevin Macksamie <>

Test app plugin like other well behaved plugins

The application plugin neither creates its tasks lazily nor references

other tasks lazily (e.g., the `jar` task). Making the

ApplicationPluginIntegrationTest inherit from WellBehavedPluginTest

exposes this problem by showing that the plugin fails the "does not

realize all possible tasks" test.

Signed-off-by: Kevin Macksamie <>

Remove dist plugin from list of misbehaving plugins

Signed-off-by: Kevin Macksamie <>

Prefer configureEach over all on dist container

Signed-off-by: Kevin Macksamie <>

Don't use deprecated capitalize method

Signed-off-by: Kevin Macksamie <>

Convert assemble/installDist tasks to be lazy

Signed-off-by: Kevin Macksamie <>

Fix xref to java-gradle-plugin section (#4179)

The xref ID for the section on the java-gradle-plugin was previously

changed from `javaGradle_plugin` to `java_gradle_plugin`. However, not

all places using the xref ID were updated to use the new ID.

Fix cross-reference in custom plugins doc

Signed-off-by: Kevin Macksamie <>