I have heard of other errors due to maven 2.0. I use 2.2.0 or 2.2.1. On Mon, Mar 15, 2010 at 6:04 PM, Benson Margulies <bimargul...@gmail.com>wrote:
> I recommend maven 2.1.x. I can't explain the error from > eclipse:eclipse, I use it constantly. > > > On Mon, Mar 15, 2010 at 7:13 PM, Jeff Eastman > <j...@windwardsolutions.com> wrote: > > After deleting my .m2 repository and rebuilding Mahout I now had an > Eclipse > > classpath full of obsolete references to various jars. I tried mvn > > eclipse:eclipse but it fails claiming the plugin is missing. Then I tried > > installing the Eclipse IAM plugin and marking the project "Use Maven > > dependency management". That lets me browse the .pom files and the > project > > structure looks more obvious than before but it zapped all the source > > directories from my classpath. If I add them back manually I have 20k > > errors. Has anybody used this plugin and can help get me sorted out > again? > > > > Jeff > > > > PS: I'm using Maven 2.0.10 > > >
