Gradle composite build with custom gradle plugin fails in IntelliJ: “Could not find method api() for...












2















I have a Gradle composite build project which contains a custom Gradle plugin. This project builds fine when using Gradle CLI, but IntelliJ fails.



I tried a few different variations on the plugin version within the resolutionStrategy block: org.test:test-plugin:0.0.1 and test-plugin:test-plugin.gradle.plugin:0.0.1 as described here: https://docs.gradle.org/current/userguide/plugins.html#sec:plugin_markers - both of those work from the CLI; changing to invalid values ("blah:blah") causes a failure.



I've made a sample Github project that contains the code to reproduce, here: https://github.com/mwmitchell/intellij-gradle-plugin-composite-build-bug along with instructions to reproduce and a workaround. The workaround is something that's not really feasible for me, as it requires repeating configuration code (dependencies, plugins etc.) and I have many, many projects that require the same/common configuration.



I would expect IntelliJ to load the project successfully, just like the CLI does. It seems like IntelliJ is loading the sub-project (:project-1:library-a) before the parent (:project-1), such that the java-library is not actually applied to the sub-project when it's evaluated.






gradle intellij-idea intellij-plugin







share|improve this question























  • Forgot to mention that I've tried Gradle 4.10.2 and Gralde 4.10.3, and my IntelliJ version is: IntelliJ IDEA 2018.3.2 (Community Edition) Build #IC-183.4886.37, built on December 17, 2018 JRE: 1.8.0_152-release-1343-b26 x86_64 JVM: OpenJDK 64-Bit Server VM by JetBrains s.r.o macOS 10.13.6

    – mmitchell
    Dec 30 '18 at 4:58













  • I've updated the README.md in the sample project on Github to show how publishing to maven local allows IntelliJ to successfully load the project. Although IntelliJ itself is unable to publishToMavenLocal due to a duplicate root project name.

    – mmitchell
    Dec 30 '18 at 6:04











  • It looks like when you build the main project from command line the :project-1:library-a project is not included into build: only one settings.gradle is allowed for the Gradle project (and gradle uses only the root's project settings.gradle file). When I import project-1 project into IDE it also builds fine for me.

    – Andrey
    Dec 30 '18 at 7:18













  • The approach I'm taking is to use includeBuild though, which from the Gradle examples/docs show that projects loaded with includeBuild are treated separately. Here's the example I originally followed: github.com/gradle/gradle/tree/master/subprojects/docs/src/… -- and then this one as well: github.com/gradle/gradle/tree/master/subprojects/docs/src/…

    – mmitchell
    Dec 30 '18 at 16:30
















2















I have a Gradle composite build project which contains a custom Gradle plugin. This project builds fine when using Gradle CLI, but IntelliJ fails.



I tried a few different variations on the plugin version within the resolutionStrategy block: org.test:test-plugin:0.0.1 and test-plugin:test-plugin.gradle.plugin:0.0.1 as described here: https://docs.gradle.org/current/userguide/plugins.html#sec:plugin_markers - both of those work from the CLI; changing to invalid values ("blah:blah") causes a failure.



I've made a sample Github project that contains the code to reproduce, here: https://github.com/mwmitchell/intellij-gradle-plugin-composite-build-bug along with instructions to reproduce and a workaround. The workaround is something that's not really feasible for me, as it requires repeating configuration code (dependencies, plugins etc.) and I have many, many projects that require the same/common configuration.



I would expect IntelliJ to load the project successfully, just like the CLI does. It seems like IntelliJ is loading the sub-project (:project-1:library-a) before the parent (:project-1), such that the java-library is not actually applied to the sub-project when it's evaluated.






gradle intellij-idea intellij-plugin







share|improve this question























  • Forgot to mention that I've tried Gradle 4.10.2 and Gralde 4.10.3, and my IntelliJ version is: IntelliJ IDEA 2018.3.2 (Community Edition) Build #IC-183.4886.37, built on December 17, 2018 JRE: 1.8.0_152-release-1343-b26 x86_64 JVM: OpenJDK 64-Bit Server VM by JetBrains s.r.o macOS 10.13.6

    – mmitchell
    Dec 30 '18 at 4:58













  • I've updated the README.md in the sample project on Github to show how publishing to maven local allows IntelliJ to successfully load the project. Although IntelliJ itself is unable to publishToMavenLocal due to a duplicate root project name.

    – mmitchell
    Dec 30 '18 at 6:04











  • It looks like when you build the main project from command line the :project-1:library-a project is not included into build: only one settings.gradle is allowed for the Gradle project (and gradle uses only the root's project settings.gradle file). When I import project-1 project into IDE it also builds fine for me.

    – Andrey
    Dec 30 '18 at 7:18













  • The approach I'm taking is to use includeBuild though, which from the Gradle examples/docs show that projects loaded with includeBuild are treated separately. Here's the example I originally followed: github.com/gradle/gradle/tree/master/subprojects/docs/src/… -- and then this one as well: github.com/gradle/gradle/tree/master/subprojects/docs/src/…

    – mmitchell
    Dec 30 '18 at 16:30














2












2








2








I have a Gradle composite build project which contains a custom Gradle plugin. This project builds fine when using Gradle CLI, but IntelliJ fails.



I tried a few different variations on the plugin version within the resolutionStrategy block: org.test:test-plugin:0.0.1 and test-plugin:test-plugin.gradle.plugin:0.0.1 as described here: https://docs.gradle.org/current/userguide/plugins.html#sec:plugin_markers - both of those work from the CLI; changing to invalid values ("blah:blah") causes a failure.



I've made a sample Github project that contains the code to reproduce, here: https://github.com/mwmitchell/intellij-gradle-plugin-composite-build-bug along with instructions to reproduce and a workaround. The workaround is something that's not really feasible for me, as it requires repeating configuration code (dependencies, plugins etc.) and I have many, many projects that require the same/common configuration.



I would expect IntelliJ to load the project successfully, just like the CLI does. It seems like IntelliJ is loading the sub-project (:project-1:library-a) before the parent (:project-1), such that the java-library is not actually applied to the sub-project when it's evaluated.






gradle intellij-idea intellij-plugin







share|improve this question














I have a Gradle composite build project which contains a custom Gradle plugin. This project builds fine when using Gradle CLI, but IntelliJ fails.



I tried a few different variations on the plugin version within the resolutionStrategy block: org.test:test-plugin:0.0.1 and test-plugin:test-plugin.gradle.plugin:0.0.1 as described here: https://docs.gradle.org/current/userguide/plugins.html#sec:plugin_markers - both of those work from the CLI; changing to invalid values ("blah:blah") causes a failure.



I've made a sample Github project that contains the code to reproduce, here: https://github.com/mwmitchell/intellij-gradle-plugin-composite-build-bug along with instructions to reproduce and a workaround. The workaround is something that's not really feasible for me, as it requires repeating configuration code (dependencies, plugins etc.) and I have many, many projects that require the same/common configuration.



I would expect IntelliJ to load the project successfully, just like the CLI does. It seems like IntelliJ is loading the sub-project (:project-1:library-a) before the parent (:project-1), such that the java-library is not actually applied to the sub-project when it's evaluated.






gradle intellij-idea intellij-plugin




gradle intellij-idea intellij-plugin






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Dec 30 '18 at 4:46









mmitchellmmitchell

112




112













  • Forgot to mention that I've tried Gradle 4.10.2 and Gralde 4.10.3, and my IntelliJ version is: IntelliJ IDEA 2018.3.2 (Community Edition) Build #IC-183.4886.37, built on December 17, 2018 JRE: 1.8.0_152-release-1343-b26 x86_64 JVM: OpenJDK 64-Bit Server VM by JetBrains s.r.o macOS 10.13.6

    – mmitchell
    Dec 30 '18 at 4:58













  • I've updated the README.md in the sample project on Github to show how publishing to maven local allows IntelliJ to successfully load the project. Although IntelliJ itself is unable to publishToMavenLocal due to a duplicate root project name.

    – mmitchell
    Dec 30 '18 at 6:04











  • It looks like when you build the main project from command line the :project-1:library-a project is not included into build: only one settings.gradle is allowed for the Gradle project (and gradle uses only the root's project settings.gradle file). When I import project-1 project into IDE it also builds fine for me.

    – Andrey
    Dec 30 '18 at 7:18













  • The approach I'm taking is to use includeBuild though, which from the Gradle examples/docs show that projects loaded with includeBuild are treated separately. Here's the example I originally followed: github.com/gradle/gradle/tree/master/subprojects/docs/src/… -- and then this one as well: github.com/gradle/gradle/tree/master/subprojects/docs/src/…

    – mmitchell
    Dec 30 '18 at 16:30



















  • Forgot to mention that I've tried Gradle 4.10.2 and Gralde 4.10.3, and my IntelliJ version is: IntelliJ IDEA 2018.3.2 (Community Edition) Build #IC-183.4886.37, built on December 17, 2018 JRE: 1.8.0_152-release-1343-b26 x86_64 JVM: OpenJDK 64-Bit Server VM by JetBrains s.r.o macOS 10.13.6

    – mmitchell
    Dec 30 '18 at 4:58













  • I've updated the README.md in the sample project on Github to show how publishing to maven local allows IntelliJ to successfully load the project. Although IntelliJ itself is unable to publishToMavenLocal due to a duplicate root project name.

    – mmitchell
    Dec 30 '18 at 6:04











  • It looks like when you build the main project from command line the :project-1:library-a project is not included into build: only one settings.gradle is allowed for the Gradle project (and gradle uses only the root's project settings.gradle file). When I import project-1 project into IDE it also builds fine for me.

    – Andrey
    Dec 30 '18 at 7:18













  • The approach I'm taking is to use includeBuild though, which from the Gradle examples/docs show that projects loaded with includeBuild are treated separately. Here's the example I originally followed: github.com/gradle/gradle/tree/master/subprojects/docs/src/… -- and then this one as well: github.com/gradle/gradle/tree/master/subprojects/docs/src/…

    – mmitchell
    Dec 30 '18 at 16:30

















Forgot to mention that I've tried Gradle 4.10.2 and Gralde 4.10.3, and my IntelliJ version is: IntelliJ IDEA 2018.3.2 (Community Edition) Build #IC-183.4886.37, built on December 17, 2018 JRE: 1.8.0_152-release-1343-b26 x86_64 JVM: OpenJDK 64-Bit Server VM by JetBrains s.r.o macOS 10.13.6

– mmitchell
Dec 30 '18 at 4:58







Forgot to mention that I've tried Gradle 4.10.2 and Gralde 4.10.3, and my IntelliJ version is: IntelliJ IDEA 2018.3.2 (Community Edition) Build #IC-183.4886.37, built on December 17, 2018 JRE: 1.8.0_152-release-1343-b26 x86_64 JVM: OpenJDK 64-Bit Server VM by JetBrains s.r.o macOS 10.13.6

– mmitchell
Dec 30 '18 at 4:58















I've updated the README.md in the sample project on Github to show how publishing to maven local allows IntelliJ to successfully load the project. Although IntelliJ itself is unable to publishToMavenLocal due to a duplicate root project name.

– mmitchell
Dec 30 '18 at 6:04





I've updated the README.md in the sample project on Github to show how publishing to maven local allows IntelliJ to successfully load the project. Although IntelliJ itself is unable to publishToMavenLocal due to a duplicate root project name.

– mmitchell
Dec 30 '18 at 6:04













It looks like when you build the main project from command line the :project-1:library-a project is not included into build: only one settings.gradle is allowed for the Gradle project (and gradle uses only the root's project settings.gradle file). When I import project-1 project into IDE it also builds fine for me.

– Andrey
Dec 30 '18 at 7:18







It looks like when you build the main project from command line the :project-1:library-a project is not included into build: only one settings.gradle is allowed for the Gradle project (and gradle uses only the root's project settings.gradle file). When I import project-1 project into IDE it also builds fine for me.

– Andrey
Dec 30 '18 at 7:18















The approach I'm taking is to use includeBuild though, which from the Gradle examples/docs show that projects loaded with includeBuild are treated separately. Here's the example I originally followed: github.com/gradle/gradle/tree/master/subprojects/docs/src/… -- and then this one as well: github.com/gradle/gradle/tree/master/subprojects/docs/src/…

– mmitchell
Dec 30 '18 at 16:30





The approach I'm taking is to use includeBuild though, which from the Gradle examples/docs show that projects loaded with includeBuild are treated separately. Here's the example I originally followed: github.com/gradle/gradle/tree/master/subprojects/docs/src/… -- and then this one as well: github.com/gradle/gradle/tree/master/subprojects/docs/src/…

– mmitchell
Dec 30 '18 at 16:30












1 Answer
1






active

oldest

votes


















0














Gradle projects can have only one settings.gradle. You can include subproject "library-a" with include 'project-1:library-a' in the main settings.gradle.






share|improve this answer
























  • Hi, I left a comment above about includeBuild vs include. From my understanding, includeBuild is supposed to provide the ability to have a composite build of independent projects. I left a few references to show more examples from the Gradle Github repo.

    – mmitchell
    Dec 30 '18 at 16:36











Your Answer






StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53975344%2fgradle-composite-build-with-custom-gradle-plugin-fails-in-intellij-could-not-f%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes









0














Gradle projects can have only one settings.gradle. You can include subproject "library-a" with include 'project-1:library-a' in the main settings.gradle.






share|improve this answer
























  • Hi, I left a comment above about includeBuild vs include. From my understanding, includeBuild is supposed to provide the ability to have a composite build of independent projects. I left a few references to show more examples from the Gradle Github repo.

    – mmitchell
    Dec 30 '18 at 16:36
















0














Gradle projects can have only one settings.gradle. You can include subproject "library-a" with include 'project-1:library-a' in the main settings.gradle.






share|improve this answer
























  • Hi, I left a comment above about includeBuild vs include. From my understanding, includeBuild is supposed to provide the ability to have a composite build of independent projects. I left a few references to show more examples from the Gradle Github repo.

    – mmitchell
    Dec 30 '18 at 16:36














0












0








0







Gradle projects can have only one settings.gradle. You can include subproject "library-a" with include 'project-1:library-a' in the main settings.gradle.






share|improve this answer













Gradle projects can have only one settings.gradle. You can include subproject "library-a" with include 'project-1:library-a' in the main settings.gradle.







share|improve this answer












share|improve this answer



share|improve this answer










answered Dec 30 '18 at 12:33









Axel PAxel P

1,77321425




1,77321425













  • Hi, I left a comment above about includeBuild vs include. From my understanding, includeBuild is supposed to provide the ability to have a composite build of independent projects. I left a few references to show more examples from the Gradle Github repo.

    – mmitchell
    Dec 30 '18 at 16:36



















  • Hi, I left a comment above about includeBuild vs include. From my understanding, includeBuild is supposed to provide the ability to have a composite build of independent projects. I left a few references to show more examples from the Gradle Github repo.

    – mmitchell
    Dec 30 '18 at 16:36

















Hi, I left a comment above about includeBuild vs include. From my understanding, includeBuild is supposed to provide the ability to have a composite build of independent projects. I left a few references to show more examples from the Gradle Github repo.

– mmitchell
Dec 30 '18 at 16:36





Hi, I left a comment above about includeBuild vs include. From my understanding, includeBuild is supposed to provide the ability to have a composite build of independent projects. I left a few references to show more examples from the Gradle Github repo.

– mmitchell
Dec 30 '18 at 16:36


















draft saved

draft discarded




















































Thanks for contributing an answer to Stack Overflow!


  • Please be sure to answer the question. Provide details and share your research!

But avoid …



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53975344%2fgradle-composite-build-with-custom-gradle-plugin-fails-in-intellij-could-not-f%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







-

Popular posts from this blog

Monofisismo

Image
Monofisismo (do grego: monos - "único, singular" e physis - "natureza") é o ponto de vista cristológico que defende que, depois da união do divino e do humano na encarnação histórica, Jesus Cristo, como encarnação do Filho ou Verbo ( Logos ) de Deus, teria apenas uma única "natureza", a divina, e não uma síntese de ambas. O monofisismo é contraposto pelo diofisismo (ou "diafisismo"), que defende que Jesus preservou em si as duas naturezas. Historicamente, o monofisismo se refere primordialmente à posição dos que (especialmente no Egito e, em menor grau, na Síria) rejeitaram as decisões do Concílio de Calcedônia em 451 (o quarto concílio ecumênico). Os membros mais moderados entre eles, porém, defendem a teologia "miafisita", que se tornou a oficial para as Igrejas Ortodoxas Orientais. Muitos ortodoxos orientais, porém, rejeitam essa classificação, mesmo como um termo genérico, mas ele é amplamente utilizado na literatura históri
Read more

Angular Downloading a file using contenturl with Basic Authentication

Image
0 I have a contentUrl when user clicks on that,file should be downloaded. If I try to browse the contentUrl in the browser it asks for Userid and password.I believe this is Basic Authentication.I dont want user to enter UserId and Password so I am passing it Authorization(Please see below code). Url looks some thing like this: http://XXX.XXX.XX.XXX:8080/flowable-rest/service/runtime/tasks/90875/attachments/90555/content let username : string = 'admin'; let pwd : string = 'test'; let headers = new Headers(); headers.set('Accept', 'text/json'); headers.append('Content-Type', 'application/json'); headers.set('Access-Control-Allow-Origin', '*'); headers.set('Access-Control-Allow-Methods','POST, GET, OPTIONS, PUT, DELETE'); head
Read more

Olmecas

Image
Monumento 1, uma das quatro cabeças colossais encontradas em La Venta, com altura aproximada de 3 metros Olmecas é a designação do povo e da civilização que estiveram na origem da antiga cultura pré-colombiana da Mesoamérica e que se desenvolveram nas regiões tropicais do centro-sul do atual México durante o pré-clássico, próximo de onde hoje estão localizados os estados mexicanos de Veracruz e Tabasco, no Istmo de Tehuantepec, numa zona designada área nuclear olmeca. A cultura olmeca floresceu nesta região aproximadamente entre 1500 e 400 a.C., [ 1 ] e crê-se que tenha sido a civilização-mãe de todas as civilizações mesoamericanas que se desenvolveram posteriormente. [ 2 ] No entanto, desconhece-se a sua exacta filiação étnica, ainda que existam numerosas hipóteses colocadas para tentar resolver esta questão. O etnónimo olmeca foi cunhado pelos arqueólogos do século XX, e não devem confundir-se com os muito posteriores olmecas-xicalancas que ocuparam vários locais do México
Read more