I’m using Gradle 6.1 release.
I define a composite build including 2 multi project (A & B) both having 2 subprojects (A1, A2 & B1, B2)
Subproject A1 uses an output of the subproject B2.
As far as I understand the documentation, it should be possible to define a project dependency within my Eclipse IDE rathen than a library dependency if a run an eclipse task from my composite build root. Am I wrong ?
Note : the module substitution as mentionned in configuration step of the Gradle log seems OK.
If I include the eclipse plugin on my composite build, I can run the “eclipse” task.
I works perfectly but only the eclipseProject on all my (sub)projects are called and not the eclipseClasspath task.
All projects evaluated.
Selected primary task 'eclipse' from project :
Selected primary task ':A1:eclipseProject' from project :A1
Selected primary task ':A2:eclipseProject' from project :A2
Selected primary task ':eclipseProject' from project :
Selected primary task ':B1:eclipseProject' from project :B1
Selected primary task ':B2:eclipseProject' from project :B2
Selected primary task ':eclipseProject' from project :
Executing A tasks [:A1:eclipseProject, :A2:eclipseProject, :eclipseProject]
Executing B tasks [:eclipseProject, :B1:eclipseProject, :B2:eclipseProject]
Then there is no link from my project B2 into my eclipse classpath of A1 project.
Maybe I didn’t get all the explanations of the composite build.