Would it not be better to define a separate scriptImplementation in the Freeplane gradle plugin?

[HaaiHenkie]

In the Freeplane gradle plugin, the source of the scripts is included in te testImplementation configuration:

sourceSets {
   test {
        groovy {
            srcDirs = ['src/test/groovy', 'src/scripts/groovy']
        }
    }
}

Now any dependencies you define for testImplementation will also apply to the Freeplane scripts. Wouldn't it be better to define a separate scriptImplementation. E.g. :

//  Implementation for scripts extends the main implementation
configurations {
    scriptsImplementation.extendsFrom implementation
}

sourceSets {
    scripts {
        groovy {
            srcDirs = ['src/scripts/groovy']
        }
    }
}

// include the dependencies of the main source set
dependencies {
    scriptsImplementation sourceSets.main.output
}

Obviously some other amendments have to be made to the Freeplane gradle plugin.

[HaaiHenkie]

I submitted pull request #11. The only thing I hesitate about is line 78-79. It seems logical to do this, but do not understand completely what this does.

[HaaiHenkie]

I now understand the purpose of line 78-79: it adds dependencies on the jars from the Freeplane installation directory to the source set. This should also be te case for the test source set, so added the original lines as line 80-81 in extra commit to pull request #11.