# Did the install task move from the maven plugin?

**URL:** <https://discuss.gradle.org/t/did-the-install-task-move-from-the-maven-plugin/6836>\
**Category:** Old Forum Archive\
**Created:** [April 10, 2013, 9:08pm UTC](https://discuss.gradle.org/t/did-the-install-task-move-from-the-maven-plugin/6836 "2013-04-10T21:08:00Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![daz](https://sea1.discourse-cdn.com/gradle/user_avatar/discuss.gradle.org/daz/32/2475_2.png) [@daz](https://discuss.gradle.org/u/daz)\
**Post date:** [April 11, 2013, 4:41pm UTC](https://discuss.gradle.org/t/did-the-install-task-move-from-the-maven-plugin/6836/5 "2013-04-11T16:41:00Z")

</div>

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?

---

_[View the full topic](https://discuss.gradle.org/t/did-the-install-task-move-from-the-maven-plugin/6836)._