I really don't understand why this version of the plugin was released without having this basic functionality in it. The settings.xml file is one of the central places that defines how Maven should behave and this plugin was released completely ignoring it.
Being the resident Maven "expert" at my company I have had at least a dozen developers say Maven is no longer working because they either upgraded to this version of the plugin or have just started to use Maven for the first time and installed the .10 version of the plugin. They all think Maven is broken now because it can't find our artifacts in our proxied repositories. It certainly doesn't help from a PR standpoint in my effort to get our company to adopt Maven as a corporate standard that is for sure. While I realize there is a beta release of the .11 version out there...the .10 version really should never have been considered a candidate for release and unfortunately not everyone knows about this forum to get the URL to the beta release. This isn't a flame...it is just the facts. From: William Ferguson [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 11, 2007 11:31 PM To: [EMAIL PROTECTED] Subject: [m2eclipse-user] Forcing Eclipse to read from M2_HOME/conf/settings.xml Hi all, how do I get Eclipse to download artifacts from the repositories that I have configured in M2_HOME/conf/settings.xml? It checks central but ignores our internal repositories - I'm guessing that its not looking at M2_HOME/conf/settings.xml at all. Is there some way to make it do so? William Eclispe 3.2 m2Eclipse 0.0.10 Maven 2.0.5
