Martin van den Bemt wrote: > > The main focus for me is that people who don't want to know about how > maven works, can still use the > benefit of making maven projects work in their IDE. Currently at our > employer everyone ditched > m2eclipse since it doesn't work at all for them and switched to > commandline, which is not an ideal > situation.
I faced a similar situation. So I compiled the latest m2eclipse code from trunk and provided a private update site. We're using the unofficial 0.10 release now and it really does work well and does everything we need for now. From what I can read m2eclipse is waiting for something in the maven embedder and then they can move forward. The m2eclipse compiled from trunk can be used with multi module projects and resolves dependencies from the Eclipse workspace. When you delete a dependency from your workspace and want to use the one provided from your build server, then you might have to do an additional clean and build within Eclipse - or sometimes even close and restart Eclipse -, but in general it does work. Stephan --- Blog http://www.stephan-schwab.com -- View this message in context: http://www.nabble.com/mevenide-vs.-m2eclipse--tf2539922s177.html#a7435592 Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
