Hello. I have a plugin that lives in

buildSrc

which provides a specialization of

Test

task types. I am trying to move it from

buildSrc

into a separate sub-project, consumed by

includeBuild

. The plugin project builds and creates its jar as expected, but the main project cannot create the tasks any more, reporting:

Could not get unknown property 'RepeatTest' for project ':geode-assembly' of type org.gradle.api.Project.

When in buildSrc the plugin is always in the classpath, with includeBuild it doesn't, so, you need to apply the plugin to have it in the classpath. (You didn't provide a lot of info so I'm just guessing here)

Sorry about that. In

settings.gradle

, I have

pluginManagement {
  includeBuild("buildSrc2")
}

and in the root

build.src

,

plugins {
  id 'org.apache.geode.gradle.geode-repeat-test'
}

which triggers the plugin project being built (i see the library, with the test-task .class) In a sub-project, I try

apply plugin: 'org.apache.geode.gradle.geode-repeat-test'

tasks.register('repeatTest', org.apache.geode.gradle.testing.repeat.RepeatTest) {}

and get

Could not get unknown property 'org' for project ':geode-assembly' of type org.gradle.api.Project

If the class is public, and you apply the plugin it should be available, yes

Inspecting the compiled class file from the subproject, i see that it is

public class RepeatTest extends Test implements GroovyObject {}

Why do you use the legacy

apply

in the sub project?

In the root project, I had been using

plugins {
  id 'org.apache.geode.gradle.geode-repeat-test' apply false
}

because the root and some others do not have tests and ergo do not need the plugin, and then using

apply

to turn it on in the

java-library

projects. I’ve tried importing, and its not able to resolve 😕

You would likely need to apply plugin in projects where you use it via plugins block. I'm not sure if adding it in the root project with

apply false

would add it to subprojects' classpath. Usually it would be done in convention plugin which will also apply java-library plugin

It should. But nevertheless, you didn't say anything that is a reason to use the legacy

apply

Oh. There is a

test.gradle

that has test logic that is added to required projects. I can’t use

plugins{}

there because it is not a project

build.gradle

. I’ll pull it up, and see if that helps.

Ah, now we have it

Yikes. You are saying to test this, I might have to migrate everything from buildscripts to better-formed plugins?

If you use precompiled script plugins, they look almost like normal build scripts

And this goes into

buildSrc

for starters, and can then be moved into an independent project if needed?

I never use

buildSrc

nowadays, but always an included build. But yes, you can also do it in

buildSrc

.

i’ll avoid buildSrc and try to move them into the cleverly-named

buildScripts