File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
The moose likes Ant, Maven and Other Build Tools and the fly likes Difference in creating Eclipse projects Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login

Win a copy of REST with Spring (video course) this week in the Spring forum!
JavaRanch » Java Forums » Engineering » Ant, Maven and Other Build Tools
Bookmark "Difference in creating Eclipse projects" Watch "Difference in creating Eclipse projects" New topic

Difference in creating Eclipse projects

Luke Murphy
Ranch Hand

Joined: May 12, 2010
Posts: 300
I have a web project specified in a maven pom.

There are two ways to make it eclipse friendly:
1. Run mvn eclipse:eclipse
2. Import it into eclipse with m2e installed and it "automatically" converts.

What's the difference? What's the best practise?

Peter Johnson

Joined: May 14, 2008
Posts: 5852

They do about the same thing. I have seen elsewhere that #2 is preferred. I also saw elsewhere that #1 was out of favor - I had expected it to be marked as deprecated when I went to the docs, but it wasn't. So I guess the real answer is: which are you more comfortable with? Do that one. Me, I would use #2 mainly because I would not think of working with a Maven project in Eclipse without m2e.

JBoss In Action
I agree. Here's the link:
subject: Difference in creating Eclipse projects
jQuery in Action, 3rd edition