Description Igor Fedorenko 2011-04-14 22:36:27 EDT

There are several scenarios when m2e does not consistently handles updated dependencies https://docs.sonatype.org/display/M2ECLIPSE/Consistent+dependency+update. We will try the following improvements for 0.13

* Introduce new "Do not automatically update dependencies from remote repositories" boolean preference. When checked (the default) m2e will force "never" global snapshot/release update policy, i.e. only resolve new/unknown artifacts from remote repositories and "never" re-resolve artifacts already present locally.

* Replace "Update Snapshots" and "Update Dependencies" right-click actions with new "Update Dependencies..." action. The new action will open a dialog similar to PDE "Update Classpath" dialog, where the user will see all workspace source-tress (!) and will be able to select projects to update. The new dialog will also provide a
** checkbox to "Forces a check for updated releases and snapshots on remote repositories" (same as -U maven cli option), off by default.
** checkbox to "Do not automatically update dependencies from remote repositories", default is off.

* Fix a bug when the same dependency can be reported as missing for some workspace projects and be available for others.