Can we remove this warning for 1.6? http://issues.gradle.org/browse/GRADLE-2745
On 15/04/2013, at 5:03 PM, Szczepan Faber <szczepan.fa...@gradleware.com> wrote: > +1 > > > On Mon, Apr 15, 2013 at 5:34 PM, Daz DeBoer <darrell.deb...@gradleware.com> > wrote: > On 15 April 2013 03:38, Luke Daley <luke.da...@gradleware.com> wrote: > > On 12/04/2013, at 8:59 PM, Daz DeBoer <darrell.deb...@gradleware.com> wrote: > > > G'day > > As reported in > > http://forums.gradle.org/gradle/topics/how_do_i_get_rid_of_packaging_deprecation_warnings_when_adding_a_dependency_on_a_war, > > there is not currently any way to resolve a 'war' module packaged for > > a maven repository without getting the deprecation warning: > > > > "Relying on packaging to define the extension of the main artifact has > > been deprecated and is scheduled to be removed in Gradle 2.0" > > > > Unfortunately, there's no way currently for a build consumer to avoid > > this warning. The intent of > > https://github.com/gradle/gradle/blob/master/design-docs/dependency-management-bug-fixes.md#correct-handling-of-packaging-and-dependency-type-declared-in-poms > > is that we only show the deprecation warning when the "type:'war'" > > attribute was not set on the dependency declaration. > > > > I think we got half way through the implementation of this story (by > > fixing > > https://github.com/gradle/gradle/blob/master/design-docs/dependency-management-bug-fixes.md#correct-handling-of-packaging-and-dependency-type-declared-in-poms), > > which meant we added the deprecation warning but never added the way > > to avoid it. > > > > I suggest that we remove the deprecation warning until we finish this > > implementation. > > +1. > > Yet another user report in the forums: > http://forums.gradle.org/gradle/topics/jhuxhorn_googlemail_com-zal6c?utm_content=topic_link&utm_medium=email&utm_source=new_topic > > -- > Darrell (Daz) DeBoer > Principal Engineer, Gradleware > http://www.gradleware.com > Join us at the Gradle Summit 2013, June 13th and 14th in Santa Clara, CA: > http://www.gradlesummit.com > > > > -- > Szczepan Faber > Principal engineer@gradleware; Lead@mockito > Join me at the Gradle Summit 2013, June 13th and 14th in Santa Clara, CA: > http://www.gradlesummit.com -- Luke Daley Principal Engineer, Gradleware http://gradleware.com Join me at the Gradle Summit 2013, June 13th and 14th in Santa Clara, CA: http://www.gradlesummit.com --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
