Jump to: navigation, search

Maven Tools 4 Eclipse

Revision as of 08:28, 5 July 2011 by Digulla.hepe.com (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Maven Tools 4 Eclipse (or m4e for short) is a set of tools to convert OSGi bundles into Maven artifacts.

You can find the project on Github: https://github.com/digulla/org.eclipse.dash.m4e.tools/

It's written in Python. I just mention this because I happen to like Python. After installing 2.7 and [1], you can forget about it.

In fact, if you just want to use the Maven artifacts in your build, go to our server at http://maven.eclipse.org/nexus/index.html

How it works

A simple workflow:

  1. Download an Eclipse release from http://www.eclipse.org/downloads/
  2. Import it into a temporary using m4e-import.py
  3. Download the sources for the Eclipse release and/or other archives which contain Eclipse products or OSGi bundles.
  4. Import them as well
  5. Merge all repositories using m4e-merge.py
  6. The sources are in the wrong place. Fix that with m4e-attach-sources.py
  7. Fix any know problems by applying the patches in the patches/ folder using the tool m4e-apply-patches.py
  8. Check the result with m4e-analyze.py
  9. Create a POM with the version info to make sure your build picks the correct versions using the m4e-dm.py tool

How you should use it

Overwhelmed? Here is a more simple version:

  1. git clone https://github.com/digulla/org.eclipse.dash.m4e.tools.git
  2. Download everything you will want and put it into the folder org.eclipse.dash.m4e.tools/downloads/
  3. run org.eclipse.dash.m4e.tools/run.sh Yes, you need Linux or MacOS for that.
  4. Grab some coffee. Not more than 12 cups per day, okay?
  5. Check the HTML file which was created for any issues that you might care about.
  6. Upload the content of org.eclipse.dash.m4e.tools/tmp/m2repo/ somewhere where Maven can find it (~/.m2/repository/ or your Maven proxy).


Please an issue for Project Dash.

Biggest Issues Right Now

  1. The name m4e sucks. [2]
  2. Rewrite the tool in Java. This would make the installation more simple but cause two new problems: Maintenance would be more expensive and the readability of the code would suffer.
  3. Find the time to create a repo with Eclipse 3.7