Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 48 Next »

Anything to do with Eclipse and Maven Integration.

Including, but not limited to:

  • Maven user's perspective: setting up an Eclipse Project derived from Maven's pom.xml
  • Maven developer's perspective: debugging Maven in Eclipse
  • Eclipse developer 's perspective: creating Eclipse artifacts (plugins, fragments, features, products, update sites, etc) via Maven

And any discussions needed to work out the design of how to get all this done and work with existing communities to pull this all together

see also: mevenide2-netbeans, maven-idea-plugin, Idea integration, ... 

Maven user

These plugins provide varying levels of support Maven Integration into Eclipse Workbench

 

maven eclipse plugin

Maven Integration for Eclipse (m2eclipse)

q4e/Eclipse IAM

Project info

 

 

 

releases

12/2005 - 2.0
02/2006 - 2.1
04/2006 - 2.2
01/2007 - 2.3
07/2007 - 2.4

05/2006 - 0.0.9
01/2007 - 0.0.10
09/2007 - 0.0.11
10/2007 - 0.0.12

08/2007 - 0.2.0
11/2007 - 0.3.0
01/2008 - 0.4.0

Open Source, License

(tick)
Apache V2

(tick)
Apache V2

(tick)
EPL 1.0 / MPL 1.1

Mailing lists

Maven lists (no dedicated ones)

users, developers, commits

users, developers, commits

issue tracking

Jira MECLIPSE

Jira  MNGECLIPSE

Google issues

wiki


Confluence

Google wiki

Maven version

any

2.1-SNAPSHOT

2.1-SNAPSHOT

hosting

Apache

Codehaus

Google

Features

 

 

 

running Maven goals from the IDE

n/a

(tick)

(tick)

Ability to cancel Maven builds

n/a

(error)

(tick)

Ability to filter Maven output (info,debug,error,downloads,...)

n/a

(tick)
"Debug Output" setting

(tick)

Automatic Eclipse classpath synchronized with Maven POM

n/a

(tick)

(tick)

Resolving dependencies from Eclipse Workspace


(tick) details

(tick)

Automatic downloading of project dependencies when POM changed


(tick)

(tick)

Automatic downloading of dependency sources


(tick)

(tick)

Dependency graph

n/a


(tick) details

Dependency analysis UI (find excluded, omitted, duplicated,... dependencies)

n/a [1]


(tick) details

New Maven 2 project wizard using archetypes

CLI


(tick)

Extensible archetype list sources (for new project wizard)

CLI


(tick)

Import local Maven 2 projects

CLI [2]

(tick) details

(tick) details

Import Maven 2 projects from VCS (CVS, SVN, etc)


(tick) SVN

(error)

Quick search dependencies on Central Maven repo

n/a

(tick) details

(error)

Quick search dependencies on Local Maven repo

n/a

(tick) details

(tick)

Quick Add dependency to POM

n/a

(tick) details

(tick)

Quick Fix in Java editor for missing dependencies

n/a

(tick) details

(error)

Basic integration with Subclipse (checkout from SVN Repositories)

n/a

(tick) details

(error)

Basic integration with Mylyn

n/a

(tick) details

(error)

Basic integration with WTP

CLI [2]

(tick) details

(error)

Debug Maven core and plugins


(tick) details

(tick) details

Debug tests launched from Maven


(tick) details

(tick) details

[1] maven-dependency-plugin provides number of goals that can be used for extensive dependency analysis
[2] maven-eclipse-plugin allow to generate eclipse project metadata, so project can be imported using import existing project wizard

Maven developer

Debug Maven using Standalone Maven install

First of all you need to get corresponding Maven projects into the Eclipse workspace.

To debug Maven standalone Maven CLI you can set the following environment variable:

Then start Maven as usual and attach remote debugger to Maven process on port 8000 using Eclipse's "Remote Java Application" configuration.

Alternatively you could create the following "Java Application" launch configuration and launch it directly from Eclipse:

Main class

org.codehaus.classworlds.Launcher

classpath

%M2_HOME%\boot\classworlds-1.1.jar

VM arguments

-Dclassworlds.conf=%M2_HOME%\bin\m2.conf
-Dmaven.home=%M2_HOME%

Program arguments

<maven cli arguments>

Debug Maven using m2eclipse

With m2eclipse you can debug Maven core and Maven plugins while running goals using m2eclipse's "Maven Build" external tools launch configuration (or from Run As / Maven * shortcut from the popup menus). Simply put a break point in the corresponding classes and switch to the Debugger perspective.

You can also configure Maven surefire plugin to not fork new JVM to run tests and then you can even debug test classes launched using "Run As / Maven test" shortcut:

Debug Maven using Q4E

Q4E launches Maven in process, not in a new jvm for performance reasons and to be able to handle events and react accordingly to them. For debugging you'll need a second jvm running in debug mode.

The easiest way to debug both Q4E, Maven and everything run by both of them is to launch a new Eclipse workspace in Debug mode.
Go to Run - Debug and create a new Eclipse Application
In the plugins tab make sure you select all Q4E plugins and click add required plugins
A new Eclipse is launched in debug mode and you could run any Maven goal through the Run - Run Menu, new Maven 2 configuration. Breakpoints in the original Eclipse will be used. Surefire should be configured not to fork the tests in this case.

If you just want to debug tests run by Maven you could configure Surefire plugin to fork with this jvm parameters

When launching a goal that runs the tests the execution will stop just before and you can go to Run - Debug - New Remote Application attaching the remote debugger to port 8000.

Eclipse developer

Building Eclipse Plugins with Maven 2: http://www.eclipse.org/articles/article.php?file=Article-Eclipse-and-Maven2/index.html

Integrate the Eclipse Web Tools Platform and Maven with m2eclipse: http://www.devx.com/Java/Article/36785

These plugins provide varying levels of support for building Eclipse artifacts with Maven

Other (or to be categorized)

  • Felix bundle
  • No labels