[GRADLE-3199] Easy way / command line option to exclude a project from multi-project builds Created: 20/Nov/14  Updated: 10/Feb/17  Resolved: 10/Feb/17

Status: Resolved
Project: Gradle
Affects Version/s: None
Fix Version/s: None

Type: Task
Reporter: Gradle Forums Assignee: Unassigned
Resolution: Won't Fix Votes: 0


While there's a command line option to exclude a (dependent) task from execution ("x/-exclude-task"), there nothing like that for the project-level in multi-project builds AFAIK.

Background: Our settings.gradle file contains the main app and examples. Usually, a developer wants to locally build both. For example, running "./gradlew lint" should run "lint" on "app" and "examples". But sometimes, we'd like to not build the examples to speed up the build. Currently, we're doing this by wrapping the "include ':examples'" directive in setting.gradle in a conditional that checks for a property, which we can set form the command line. But unfortunately this does e.g. not work with Android Studio [1]. So simply having an --exclude-project command line option would be nice.

[1] [1]https://code.google.com/p/android/iss...
[1] https://code.google.com/p/android/issues/detail?id=80193

Comment by Gradle Forums [ 20/Nov/14 ]

You could just run `gradlew lint` from the `app` directory, or run `gradlew :app:lint` from the top.

Comment by Gradle Forums [ 20/Nov/14 ]

True, for my simplified example that would work. But the app is in fact split into multiple library projects. What you suggest would only run lint on the app code, but what I'd like to do is to run lint on the app and all (dependent) library projects, but not the example code.

Comment by Gradle Forums [ 20/Nov/14 ]

You could model that as a task that depends on all non-example lint tasks.

Comment by Gradle Forums [ 20/Nov/14 ]

Sure. But my point is that I believe this is such a common requirement that there should be no need to model a task, but that Gradle should provide some built-in means to accomplish that.

Comment by Benjamin Muschko [ 15/Nov/16 ]

As announced on the Gradle blog we are planning to completely migrate issues from JIRA to GitHub.

We intend to prioritize issues that are actionable and impactful while working more closely with the community. Many of our JIRA issues are inactionable or irrelevant. We would like to request your help to ensure we can appropriately prioritize JIRA issues you’ve contributed to.

Please confirm that you still advocate for your JIRA issue before December 10th, 2016 by:

  • Checking that your issues contain requisite context, impact, behaviors, and examples as described in our published guidelines.
  • Leave a comment on the JIRA issue or open a new GitHub issue confirming that the above is complete.

We look forward to collaborating with you more closely on GitHub. Thank you for your contribution to Gradle!

Comment by Benjamin Muschko [ 10/Feb/17 ]

Thanks again for reporting this issue. We haven't heard back from you after our inquiry from November 15th. We are closing this issue now. Please create an issue on GitHub if you still feel passionate about getting it resolved.

Generated at Wed Jun 30 12:42:36 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.