The deprecation warning is problematic, as there are many cases where you can’t do anything about it. You’ll just need to ignore it until we come up with either: 1. A proper solution to this problem 2. A way to ‘acknowledge’ a deprecation warning so that it stops displaying.
Regarding the snapshot versions generated by the ‘maven-publish’ plugin, there is no way to make Gradle use a non-unique snapshot for the ‘PublishToMavenLocal’ task. This could be a bug: what happens when you “install” a snapshot artifact using Maven 3?