On 25/02/2013, at 9:23 PM, Luke Daley wrote:

> Hi,
> 
> We've had a report that we don't correctly honour Ivy private configurations, 
> in that we allow access to them.
> 
> Is this something we intend to fix?

We should. It would have to be via a deprecation, I think.

The new publishing plugins don't generate any private configurations, so a 
'workaround' would be to switch to use them.

> 
> Begin forwarded message:
> 
>> From: Gradle <[email protected]>
>> Subject: New reply: Why does not Gradle fail if resolving a private 
>> configuration
>> Date: 25 February 2013 10:20:24 AM GMT
>> To: Gradle <[email protected]>
>> 
>> Detelin replied to Why does not Gradle fail if resolving a private 
>> configuration, a question about Gradle.
>> 
>> We have a multi-project build that uses Gradle (most of our builds are using 
>> Gradle). Some modules happen to reference other module's private 
>> configurations, and this did not cause any problems - in fact we did not 
>> actually notice it, until a project that uses Apache Ivy attempted to 
>> reference those modules and got a resolution failure (e.g. `configuration 
>> not public in org.foo#bar;1.0.0`). 
>> 
>> So now we are trying to modify all these projects to reference just the 
>> public configurations - for example if a project is referencing other 
>> project's `providedCompile` configuration, which is private, we are changing 
>> it to `providedRuntime` (these are custom provided configuration we've 
>> introduced). 
>> 
>> But in general, I think it would be good if Gradle detects and reports such 
>> cases since otherwise it will be impossible for anyone using Apache Ivy to 
>> resolve those modules - and I guess there is an overall thinking that ivy 
>> metadata produced by Gradle can be consumed with Apache Ivy.
>> 
>> Go look at this reply | Stop following this question
>> 
>> 
>> This message sent from the Gradle community on Get Satisfaction. 
>> To unsubscribe or change your email settings, click here.
>> 
>> 
>> ----------------
>> Create a customer community for your company at GetSatisfaction.com.
>> 
> 
> -- 
> Luke Daley
> Principal Engineer, Gradleware 
> http://gradleware.com
> 


--
Adam Murdoch
Gradle Co-founder
http://www.gradle.org
VP of Engineering, Gradleware Inc. - Gradle Training, Support, Consulting
http://www.gradleware.com

Reply via email to