We shouldn't support anything but Maven itself. Its up to the IDEs to support Maven then. If IntelliJ does it better then maybe people will favor it but that's up to the user. I don't think we should favor any IDE by itself. On Dec 5, 2011 7:41 PM, "Jeff Eastman" <[email protected]> wrote:
> I will check that out today and report back. > > The larger issue I see is that, by doing all of our maven development in > IntelliJ and not keeping Eclipse working as a viable IDE option, that we > are not doing a good job of supporting our customer base. All the shops > I've worked in for the last ten years have been Eclipse shops. I echo > Benson's concern about the amount of neural energy needed to make the > switch, and forcing that switch in order to do Mahout-based development > will certainly make us less useful in those organizations which, for better > or worse, are Eclipse shops too. > > I don't know yet what issues are preventing me from working in Eclipse > Indigo + m2e 1.0 but they are reproducible and I think it is a very high > priority to figure them out and resolve them. > > Jeff > > On 12/4/11 6:39 PM, Ted Dunning wrote: > >> Do the eclipse files that I posted on dropbox do any good for eclipse? >> >> On Sun, Dec 4, 2011 at 5:04 PM, Benson >> Margulies<bimargulies@gmail.**com<[email protected]> >> >wrote: >> >> If you can add intellij helpfulness to the mahout tree, please do. >>> >>> On Sun, Dec 4, 2011 at 7:44 PM, Ted Dunning<[email protected]> >>> wrote: >>> >>>> Can't intelliJ export eclipse projects? (it has a menu item with that >>>> promise) >>>> >>>> Take a look at >>>> http://dl.dropbox.com/u/**36863361/eclipse.tgz<http://dl.dropbox.com/u/36863361/eclipse.tgz>which >>>> is the >>>> result me doing that on a modified mahout directory. >>>> >>>> If that shows promise, I can do it on trunk. >>>> >>> >
