On 7/3/2012 5:01 AM, Peter Klügl wrote: > Hi Marshall, > > thanks for the information. > > Just a short question so that I might understand the maven stuff a bit more. > > This lifecylce mapping deactivates the mentioned goals and therefore some > projects cannot be built with m2e, e.g., the runtime plugin because of the > inclusion of the other projects, right?
Hmm, I don't quite understand what you're saying. But I think there are maybe 3 styles of building: 1) The "automatic" build of the Eclipse workspace, or the build that happens when you pick Eclipse's menu -> project -> clean. 2) The build that happens (with or without Eclipse running) when you use the "mvn" command from a command line. 3) The build that happens when you right-click a project and select Run and then pick a maven build action. #2 and #3 I think run essentially outside of Eclipse using the normal maven infrastructure and maven plugins. #1 is the only one that m2e is affecting. Now, the way m2e does various actions when building seems to be to call the underlying maven plugin (except perhaps sometimes, when the m2e developers determined that the plugin was too buggy). See http://wiki.eclipse.org/M2E_Extension_Development for an example. In my building of things, the Eclipse plugin projects are not built in style #1. When I need to build them, I use #2 or #3. I don't think there's a connector bridge (yet) for the felix bundle plugin. > > I observe this when I build UIMA and was wondering if this is normal to add > the mapping in order to get rid of the (m2e) problems. I did this in my > workspace, but haven't seen any comments on the webpage about that. However, > all works fine when I build the projects directly with "run as maven build... > package". Please correct me, if I got something wrong. I think you are correct. "run as maven build... package" is the style #3 above. -Marshall
