Gradle Project Discoverer - 1.3

Extension ID

com.castsoftware.dmtjeegradlediscoverer

What’s new?

See Release Notes.

What is discovered?

The Gradle Project Discoverer detects following project types :

Java/Android projects built with Gradle (single as well multimodule)

Discovery is based on the presence of *.gradle files in the Application source code. The extension considers the following project build files to discover corresponding Gradle Java/Android projects:

• settings.gradle
• build.gradle
• dependency.gradle(any external file that is imported in build.gradle using “apply from”)

For Android specific projects, the Gradle discoverer ≥ 1.1.6 will discover the folder containing the AndroidManifest.xml file as part of the “Resource” files - this will appear as shown below:

Kotlin projects built with the Kotlin Gradle Plugin (single as well multimodule)

Discovery is based on the presence of *.gradle.kts files in the Application source code. The extension considers the following project build files to discover corresponding Gradle Java projects:

• settings.gradle.kts
• build.gradle.kts
• dependency.gradle.kts (any external file that is imported in build.gradle.kts using “apply from”)

*.fxml file support

*.fxml files will be included in the analysis scope when .gradle / .gradle.kts files are discovered in the project source code.

References required

All .gradle / .gradle.kts files MUST contain at least one reference to the plugins listed below either using the apply plugin option or using the plugin command mentioned below.

\\apply plugin references:

apply plugin: 'java'
apply plugin: 'maven'
apply plugin: '%android%'
apply plugin: 'application'
apply plugin: '%gradle%'
apply plugin: '%kotlin%'

\\plugin command references:

plugins
{
    id : 'java'
}

plugins
{
    id : 'maven'
}

plugins
{
    id : '%android%'
}

plugins
{
    id : 'application'
}

plugins
{
    id : '%gradle%'
}

plugins
{
    id : '%kotlin%'
}

In what situation should you install this extension?

When you want to discover and select all the Gradle projects from your source code. The extension reads all the projects based on their respective *.gradle or *.gradle.kts file.

Function Point, Quality and Sizing support

• Function Points (transactions): a green tick indicates that OMG Function Point counting and Transaction Risk Index are supported
• Quality and Sizing: a green tick indicates that CAST can measure size and that a minimum set of Quality Rules exist

Compatibility

Exclusion rules

The following exclusion rules are provided:

These options are exposed in the CAST Delivery Manager Tool (but not in AIP Console):

Delivery messages

The following messages emitted by the discoverer may appear during the source code delivery:

Results after using the discoverer

Gradle Java projects will be selected by default - example shown for the CAST Delivery Manager Tool:

Notes

src/main/java directory

Gradle defines the directory src/main/java as the default source directory for compilation (reference: https://docs.gradle.org/current/userguide/organizing_gradle_projects ). Therefore, the Gradle extension works in exactly the same way, it will add the src/main/java as the default source directory if no source directories are explicitly mentioned in the build.gradle file within the sourceSet block.

As a result of this, there may be scenarios where we do not have src/main/java folder for project modules structure but still it shows src/main/java as source directory in discovery files, if discovered. In these scenarios, the discovered Gradle modules will be shown as “Deactivated”.

Required Maven repositories

Contrary to pure Maven projects, Maven repositories used by Gradle projects will not be fetched and included by default, therefore, if your Gradle project uses any Maven repositories, you must ensure that these repositories are delivered manually.