|
| Re: m2eclipse or running mvn as external program? [message #175221 is a reply to message #175197] |
Wed, 18 October 2006 13:11   |
Eclipse User |
|
|
|
Originally posted by: wayne.beaton._NOSPAM_eclipse.org
Steinar Bang wrote:
> What do others recommend for running maven 2 builds from inside eclipse,
> the m2eclipse plugin (http://m2eclipse.codehaus.org/), or running mvn
> as an external program?
>
> The m2eclipse plugin seems to have most promise, in that it's able to
> update the classpath and dependencies of the projects it builds.
>
> But the m2eclipse home page seems a bit out of date, there isn't any
> documentation outside of the flash demo, and I haven't been able to
> google up any archives for the mailing lists listed on the home page,
> so I haven't been able to determine the activity level for the
> project.
>
> And also a search match I dug up yesterday, mentioned
> incompatibilities between the eclipse:eclipse target of the maven
> eclipse plugin, and m2eclipse:
> http://permalink.gmane.org/gmane.comp.jakarta.turbine.maven. user/47974
>
> Does anyone know more about this?
>
> Thanx!
>
>
> - Steinar
>
>
There is an Eclipse Corner article-in-progress in bugzilla that might
help you out. Frankly, I'd love it if you could attach your reviewer
comments to the piece...
https://bugs.eclipse.org/bugs/show_bug.cgi?id=158653
Wayne
|
|
|
| Re: m2eclipse or running mvn as external program? [message #175748 is a reply to message #175221] |
Fri, 20 October 2006 17:33 |
 Steinar Bang
Messages: 108
Registered: July 2009 |
Senior Member |
|
|
>>>>> Wayne Beaton <wayne.beaton@_NOSPAM_eclipse.org>:
> Steinar Bang wrote:
> There is an Eclipse Corner article-in-progress in bugzilla that
> might help you out. Frankly, I'd love it if you could attach your
> reviewer comments to the piece...
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=158653
Thanx for the tip!
Although it doesn't mention m2eclipse at all, it did provide the clue
to make m2eclipse work: the actual maven project was a parent
directory of the directories made into eclipse projects by the maven
eclipse plugin ("mvn eclipse:eclipse"), which were the ones I tried
importing into the workspace earlier.
Importing the top level maven project as an eclipse didn't work. But
creating a new eclipse Java project from that directory _did_ work.
And _then_ m2eclipse magically started working, and the POM became the
master (as your article outlines).
As an example of how it works: I edited the pom.xml and changed the
JUnit version from 3.8.1 to 4.1, and saved the pom.xml file. And
m2eclipse promptly downloaded JUnit 4.1, installed it in my maven
repo, and modified the project's class path to use that JAR instead
the 3.8.1 one.
I wonder if, and how, m2eclipse would play together with your
MOJOs...?
|
|
|
Powered by
FUDForum. Page generated in 0.08364 seconds
] 
Search
Help
Register
Login
Home
