Custom Gradle Plugin as Standalone project

In stead of placing your gradle plugins in the buildSrc folder or directly in the build.gradle file then you have the option to place it it a standalone project. This gives the option to use the same plugin between multiple plugin consumer projects!
Enjoy! :-)
Feel free to leave a comment or question.
The code is located here:
github.com/eki...
github.com/eki...
Follow me on twitter:
/ mikemoelnielsen

[@madhes23]

This is one of the best resources on the internet for learning about standalone plugins. Thanks man!

[@MikesTechCorner]

Thank you very much. :-)

[@noboddy_knows]

was struggling looking at the official documentation here is a nice explanation

[@MikesTechCorner]

Thank you for watching and giving me feedback. :)

[@carlosmspk]

Hats off for an easy to reproduce, and minimalist example.
Would love it if you could follow up with some common use cases, such as pushing artifacts to a remote database or something a bit more complex that most people probably could benefit from!

[@MikesTechCorner]

Good suggestion. Thank you for watching

[@strok777]

Has anyone experienced that when exporting the plugin to a local repository the gradle.plugin container is not created but it is when exporting it to mavenLocal?

[@MikesTechCorner]

No I haven't seen that.

[@aleksei4604]

Thanks for your tutorial
For me it works such way
pluginManagement {
repositories {
maven {
mavenCentral()
url = '...'
}
}
}
Because Gradle could not find org.codehaus in repo (url)

[@MikesTechCorner]

Thanks for sharing!

[@carlosmspk]

That's odd, it worked for me...