[GRADLE-1314] more selective Exclusion by the provided* Configurations ? Created: 18/Jan/11  Updated: 10/Feb/17  Resolved: 10/Feb/17

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

Type: Improvement
Reporter: Helmut Denk Assignee: Unassigned
Resolution: Won't Fix Votes: 0


 Description   

situation

build of a war

 
dependencies {
  compile 'org.clojure:clojure:1.2.0' (***)
  compile 'org.clojure:clojure-contrib:1.2.0'
  
  compile 'compojure:compojure:0.5.3'
  compile 'ring:ring-core:0.3.4' (**)
  compile 'ring:ring-devel:0.3.4'
  compile 'ring:ring-servlet:0.3.4'

  providedCompile 'javax.servlet:servlet-api:2.5' 
  providedCompile 'ring:ring-jetty-adapter:0.3.4' (*)
}

ring-jetty-adapter(*) has a dependeny on ring-core-0.3.4(**), jetty et al.

 
<dependency>
  <groupId>ring</groupId>
  <artifactId>ring-core</artifactId>
  <version>0.3.4</version>
</dependency>
<dependency>
    <groupId>org.mortbay.jetty</groupId>
    <artifactId>jetty</artifactId>
    <version>6.1.14</version>
</dependency>

ring-core(**) has a dependeny on clojure-1.2.0 (***) et al.

 
<dependency>
  <groupId>org.clojure</groupId>
  <artifactId>clojure</artifactId>
  <version>1.2.0</version>
</dependency>

problem

clojure-1.2.0 is resolved for compile but not packed
into the war because it's excluded via providedCompile.

analysis

by helmut denk:

"should'nt clojure-1.2.0 be packed into the war because
the compile-configuration has a dependency on it and
thus it is (probably) needed during runtime ?

of course jetty should still be excluded from being packed
into the war."

by peter niederwieser:

"I agree that org.clojure:clojure should be contained in the War."

references

http://gradle.1045684.n5.nabble.com/Exclusion-by-the-provided-Configurations-td3338016.html

 Comments   
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 11:52:24 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.