[GRADLE-2529] Embedding Gradle (Tooling API) is inconvenient due to number of jars Created: 23/Oct/12  Updated: 17/Jan/13  Resolved: 03/Dec/12

Status: Resolved
Project: Gradle
Affects Version/s: None
Fix Version/s: 1.4-rc-1

Type: Improvement
Reporter: Szczepan Faber Assignee: Unassigned
Resolution: Fixed Votes: 0


Embedding Gradle via tooling API is somewhat inconvenient. The number of jars seems to be slowly growing and since Gradle 1.1 it also incudes jars that might clash with client jars:


  • Ideally, the tooling-api ships in a single jar that only contains what's really needed.
  • We should consider repackaging the 3rd party libs to avoid conflicts

This inconvenience might lead to incorrect use of the Tooling API. Like in JetGradle, the jars are autodiscovered from the user provided gradle installation which leads to various awkward problems (the tooling api jars and its dependencies must be included in the client distribution, not autodiscovered).

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