As I "confused user", there is another "problem"; I get one deprecation warning in my build, but it is not in my build script (getClasses --> getOutput or something like that). And go hunting for it in plugins doesn't seem to be "my job", UNLESS the warning contained the LOCATION (preferably the plugin name + file).
Cheers Niclas On Wed, Mar 7, 2012 at 12:18 AM, Peter Niederwieser <[email protected]> wrote: > One thing to keep in mind is that third-party plugin authors will often want > to keep using a deprecated element as long as possible in order to stay > compatible with the widest possible range of Gradle versions. Therefore, > it's important to have a binding statement like "elements deprecated in 1.x > will be removed in 2.0 (but no sooner)". > > Cheers, > Peter > > -- > View this message in context: > http://gradle.1045684.n5.nabble.com/Deprecation-tp5541189p5541377.html > Sent from the gradle-dev mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > -- Niclas Hedhman, Software Developer http://www.qi4j.org - New Energy for Java I live here; http://tinyurl.com/3xugrbk I work here; http://tinyurl.com/6a2pl4j I relax here; http://tinyurl.com/2cgsug --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
