In this build, only the ':foo' subproject has had the java
plugin applied.
As expected, only the ':foo' project has java
-plugin related tasks, e.g. assemble
.
However, both the ':foo' and ':foo:bar' subprojects have source sets configured.
Why does the ':foo:bar' subproject have source sets at all? Is this a bug?
$ gradle --version
[...]
Gradle 2.12
$ gradle projects
-----------------------------------------
--- root project 'my-project'
---
--- tasks: []
-----------------------------------------
-----------------------------------------
--- project ':foo'
---
--- tasks: [task ':foo:assemble', task ':foo:buildDependents', task ':foo:buildNeeded', task ':foo:check', task ':foo:classes', task ':foo:compileJava', task ':foo:compileTestJava', task ':foo:jar', task ':foo:javadoc', task ':foo:processResources', task ':foo:processTestResources', task ':foo:test', task ':foo:testClasses']
--- sourceSets: [source set 'main', source set 'test']
-----------------------------------------
-----------------------------------------
--- project ':foo:bar'
---
--- tasks: []
--- sourceSets: [source set 'main', source set 'test']
-----------------------------------------
:projects
------------------------------------------------------------
Root project
------------------------------------------------------------
Root project 'my-project'
\--- Project ':foo'
\--- Project ':foo:bar'
To see a list of the tasks of a project, run gradle <project-path>:tasks
For example, try running gradle :foo:tasks
BUILD SUCCESSFUL
Total time: 0.766 secs