|Re: [tycho-user] M2 or plain Maven for Tycho?|
Well, I wouldn't expect m2eclipse to help you with Tycho projects.
If you have a Maven-based project, like a web application, that you're developing in Eclipse, then you already have dependencies and various goals in the pom.xml. The m2eclipse plug-in will help you leverage all of that Maven pom.xml information within Eclipse. It exposes the pom.xml dependencies to your Eclipse project in a way that the Eclipse IDE can use them so that you don't have to set up the libraries again inside of Eclipse. It installs its own builder so that it can run Maven for you. etc.
Tycho is almost exactly the other way around. If you have an Eclipse plug-in that you're developing in Eclipse, then you already have dependencies and other build properties encoded in the Eclipse PDE files like MANIFEST.MF, build.properties, and feature.xml. It *already* works in Eclipse, and you don't need m2eclipse's help. The point of Tycho is to help you leverage all of that Eclipse PDE MANIFESET.MF and other information within Maven. It translates the dependencies from your Eclipse PDE files and presents them to Maven in a way that Maven can use so that you don't have to set up all of the dependencies again inside of a pom.xml file. That way, you can take a functioning Eclipse plug-in, feature, and/or product and create a headless (command line) Maven build without repeating a bunch of stuff in your pom.xml files.
Back to the top