Skip to content

When creating a Gradle multi-project, which has a custom-named main build-file, it doesn't recognize subprojects, and only gets the root one.

Notifications You must be signed in to change notification settings

lucasvc/gradle-multi-project-custom-buildfilename

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

4 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Gradle multi-project, using a custom-named main build-file

This project shows an issue with Gradle multi-projects. When the main build script has custom name, the call to gradle command should be:

./gradlew --no-daemon --build-file custom-name.gradle tasks

The settings.gradle file includes the children projects, (and it is processed, at least the println). But when listing all the projects from main build script only the root project appears:

<settings> :client
<settings> :service
<custom> [root project 'gradle-multi-project-custom-buildfilename']
> rootProject.name: gradle-multi-project-custom-buildfilename
> project.name: gradle-multi-project-custom-buildfilename
:tasks
...

It does not apply the rootProject.name property neither. Does not work even adding the --settings-file flag to the command line.

Asked in this thread from Gradle forums if this is an expected behaviour.

Tested with Gradle 3.0 and 3.2.1 (uploaded wrapper 3.2.1).

About

When creating a Gradle multi-project, which has a custom-named main build-file, it doesn't recognize subprojects, and only gets the root one.

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published