Jeff, This area is on my list.
--benson On Tue, Mar 16, 2010 at 11:17 AM, Jeff Eastman <j...@windwardsolutions.com> wrote: > Thanks guys, I upgraded maven to 2.2.1 and eclipse:eclipse finally ran. The > Eclipse IAM plugin did not seem to understand the poms so I removed it and > installed m2eclipse instead. At least that has some user documentation but I > still can't get it to do anything useful. Grrr. > > > Ted Dunning wrote: >> >> 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 >>>> >>>> >> >> > >
