[GRADLE-2231] Tooling API: Provide ability to distinguish 'compile' from 'providedCompile' dependency scope Created: 13/Apr/12  Updated: 10/Feb/17  Resolved: 10/Feb/17

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

Type: Bug
Reporter: Denis Zhdanov Assignee: Unassigned
Resolution: Won't Fix Votes: 9


The gradle api returns scope 'compile' for the dependencies declared as 'providedCompile'. However, the reference states the following:

The War plugin adds two dependency configurations: providedCompile and providedRuntime. Those configurations have the same scope as the respective compile and runtime configurations, except that they are not added to the WAR archive

That means that a Tooling API client doesn't have an ability to configure the *.war assembling rules properly without correct scope information.

Comment by Szczepan Faber [ 24/Apr/12 ]

Is it enough if the tooling api provides the information if the dependency should be deployed or not?

Comment by Denis Zhdanov [ 02/May/12 ]

I think we can elaborate that further - it would be really convenient for the end-users if the IDE is able to configure assembling rules (not only for wars but for ordinary jars as well, see http://www.jetbrains.com/idea/webhelp/artifact.html) based on the information contained at the build.gradle.

I.e. the tooling api should expose that information in general, taking into account all custom layout changes introduced by the end-user.

Comment by Szczepan Faber [ 18/May/12 ]

It's blocking this JetGradle feature: http://youtrack.jetbrains.com/issue/IDEA-84589

Comment by Dieter Rehbein [ 19/Jun/12 ]

a workaround, that worked for me:

war {
   classpath = files(configurations.runtime.minus(configurations.providedCompile))
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:16:18 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.