14

my gradle build outputs the message

Deprecated: relying on packaging to define the extension of the main artifact is deprecated, and will not be supported in a future version of Gradle.

What does this mean and how to make the warning go away?

Cengiz
  • 5,375
  • 6
  • 52
  • 77
  • What artifacts does your build produce, and how are they defined? – Tom Anderson Oct 17 '12 at 12:46
  • If your context is Android development, with the Android Gradle plugin, see this instead: http://stackoverflow.com/questions/21496956/gradle-deprecation-relying-on-packaging-to-define-the-extension-of-the-main-art – Jonik Sep 02 '14 at 08:41

3 Answers3

6

How to solve this issue is discussed there: http://forums.gradle.org/gradle/topics/jhuxhorn_googlemail_com-zal6c

For now, no solution, the warning is said to be 'bugged'.

Vincent Cantin
  • 16,192
  • 2
  • 35
  • 57
2

It seems there is currently no fix for the issue. The bug has been filed here: https://code.google.com/p/android/issues/detail?id=65501

Dick Lucas
  • 12,289
  • 14
  • 49
  • 76
0

It is saying you depend on some artefact of a type that it does not know about but that it can find by using the "packaging" attribute of the pom. There are enhancements planned here and they are described here.

DaveShaw
  • 52,123
  • 16
  • 112
  • 141
Matt
  • 8,367
  • 4
  • 31
  • 61
  • 27
    This answer could be enhanced by suggesting how to fix the actual warning. The linked resource doesn't help explain how to make the warning go away. – Ari Maniatis Apr 02 '13 at 09:46
  • 1
    to do that, I'd be answering a question that wasn't asked and would need more information from the OP anyway (the specifics of what that dependency is & how it is declared) hence IMV a downvote seems rather harsh – Matt Apr 02 '13 at 10:03
  • 2
    How to solve this issue is discussed there: http://forums.gradle.org/gradle/topics/jhuxhorn_googlemail_com-zal6c For now, no solution, the warning is said to be 'bugged'. – Vincent Cantin Sep 16 '13 at 10:17