Upgrading to IntelliJ 12 has fixed this prob! Thanks
On Tue, Apr 30, 2013 at 2:39 PM, Andrew Musselman < andrew.mussel...@gmail.com> wrote: > PS IntelliJ Community Edition 11.1.5 for Linux > > > On Tue, Apr 30, 2013 at 2:36 PM, Andrew Musselman < > andrew.mussel...@gmail.com> wrote: > >> Get the svn repo from here? >> https://cwiki.apache.org/MAHOUT/buildingmahout.html >> >> svn co http://svn.apache.org/repos/asf/mahout/trunk >> >> >> >> On Tue, Apr 16, 2013 at 8:11 PM, Ted Dunning <ted.dunn...@gmail.com>wrote: >> >>> This still isn't right. >>> >>> WHat happens if you clone mahout again (to get a clean copy) and then >>> open >>> the pom file using a clean start of IntelliJ? >>> >>> This will avoid question of cached evil. >>> >>> Also, which version of IntelliJ are you using? >>> >>> >>> On Tue, Apr 16, 2013 at 11:10 PM, Andrew Musselman < >>> andrew.mussel...@gmail.com> wrote: >>> >>> > On Tue, Apr 16, 2013 at 3:14 PM, Ted Dunning <ted.dunn...@gmail.com> >>> > wrote: >>> > > >>> > > >>> > > > Cool, thanks; I fixed it by adding the generated-sources/org >>> directory >>> > to >>> > > > the source path.. >>> > > > >>> > > >>> > > That isn't a good fix. For one thing, you may have a similar problem >>> > with >>> > > tests. And if we add protobuf sorts of things, that will fail as >>> well. >>> > >>> > >>> > Using "compile" in the Maven tab doesn't do the trick. >>> > >>> > > >>> > > > Still have IntelliJ complaining about a bunch of things in the >>> > top-level >>> > > > pom.xml, like hadoop module dependencies not found, maven plugins >>> not >>> > > > found, etc.. >>> > > > >>> > > >>> > > That means that your environment has a problem. >>> > > >>> > > What version of Maven do you have installed? Did you tell IntelliJ >>> about >>> > > your installation? >>> > > >>> > >>> > Maven 3.0.4, and yes >>> > >>> >> >> >
