Details
-
Sub-task
-
Status: Closed
-
Major
-
Resolution: Abandoned
-
Trunk, Upcoming Branch
-
None
-
None
-
Bug Crush Event - 21/2/2015
Description
I posted a related message in dev ML: https://markmail.org/message/55r5ycn2wrbotnbn:
Hi,
I just read a members thread about this article: https://medium.com/@alex.birsan/dependency-confusion-4a5d60fec610
One member mentioned that the Groovy project is using the Gradle's dependency verification feature[1] in the Apache Groovy build.
I suggest we do the same, even after the move from JCenter to MavenCentral where things should be safer.
What do you think?
[1] https://docs.gradle.org/current/userguide/dependency_verification.html
Jacques
Note that dependency verification is an incubating feature. So we will wait before backporting from trunk...