Running tasks of custom plugin which lies in the same project but also is published to a private repository

[Zerg (Rush)]

Hi,

i would need some help since im kind of coming to an end with my problem solving skills.

Before starting with the description i just want to point out which forums i already saw/tried:

How can I apply a custom plugin, that resides in the buildSrc folder of the root project to all subprojects?

I have a multiproject build. In the buildSrc folder, there is a plugin A, which needs to be applied to all subprojects. I tried applying the plugin like this in the root buildscript: subprojects { //... apply plugin:'A' } However I get an error, that the plugin with id ‘A’ is not found. So how can I apply the plugin in all subprojects?

Multi-project build and custom plugin under buildSrc - plugin not found

Hi, I have a simple plugin class in groovy in ROOT/buildSrc/src/main/groovy/org/example/Foo.groovy and a build file located at ROOT/sub1/test.gradle, which contains the following: apply plugin: org.example.Foo Now if I do a $ ./gradlew -b test.gradle in folder sub1, I get this error: > Could not find property 'org' on project 'sub1'. If I add an import statement at the top of test.gradle import org.example.Foo I get a ClassNotFoundException. I also tried assigning a short name to my pl…

How do I add classpath entries so that buildSrc plugin can find my files in gradle?

Unfortunately, none of them helped.

I have a project with an for now empty build.gradle and the buildSrc-folder (also a settings.gradle with project-name and a gradle-wrapper).
In the buildSrc i have the project which holds the custom plugin. In there the build.gradle applies all the needed plugins for publishing jars and managing the groovy-files/tasks. When i call gradle uploadArchives everything works fine, it uploads, and i can even apply the plugin in other projects. But for testing when the repository is not available or just for quick local hacks i would like to be able to call the plugin-tasks from the overlying project.
This sadly fails, as gradle states that the plugin with the given id cannot be found. One post said that you have to write .class to apply plugins which are in the classpath (through buildSrc-compiling) but this fails with the exact same message.

Here again the structure:
-proj1
-build.gradle
-buildSrc (proj1-1)
-build.gradle
-build (with the groovy-classes)
-src
-main
-groovy (with all the tasks in the correct package)
-resources (with the defined plugin-id)
-test

Does anyone have an idea what could be wrong?

Thanks in advance and im happy to serve any more information if needed!

regards Zerg

[Gary_Hale]

What error are you getting? How is your buildSrc directory laid out? Do you have a public example (on github or elsewhere) that you can share?