-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can you provide a Spring Boot + Kotlin sample? #19
Comments
Hi @patrick-at-ifood. To understand this error one hast to understand that Gradle can load different sets of plugins for each (sub)project. However, some plugins – like the Kotlin Gradle plugin – cannot deal with this and give such errors. To avoid this, we have to "force" Gradle to load the same plugins for all (sub)projects. The current setup of this project may cause this, because the plugins are split up into multiple "plugin projects". From each of this projects, a Jar is created (containing all the plugins of the corresponding project). The Jars are only loaded by a project, if a plugin from the Jars is used (a lot of Gradle magic). current structure
I plan to change the setup of this project, to only have one plugins project. Issues like this and my own experience in multiple projects showed, to me, that this splitup has mostly disadvantages. (Note: we discussed this topic here.) new structure
All external plugins should then be in the dependencies block of that one
Would that change be possible in you case and does it solve the issue for you? |
I believe that might work just fine, looks to me that it even makes things easier. |
👍 It's still work in progress, but I have started work on updating this project and have a branch that follows the setup I was talking about: https://github.com/jjohannes/gradle-project-setup-howto/tree/next_iteration/ |
The new setup is now on With this structure, I combined the |
I am trying to setup it by myself and keep getting the
The Kotlin Gradle plugin was loaded multiple times
message.The text was updated successfully, but these errors were encountered: