I am not sure <execute> mapping is a good idea in your case. At least set runOnIncremental=false to only run it after clean build.
There are couple of bugs in m2e bugzilla that talk about Maven console oddities, but nobody cared enough to provide a patch -- Regards, Igor On 12-08-15 10:56 PM, Nathaniel Mishkin wrote:
Ah, yes, I've looked at that wiki page many times, but I guess its words and my experience have steered me strongly enough away from ever doing <action><execute/></action> that I forgot to just try that. I just did that and it seems to do what I want. As far as the background on the m2e builder, I guess I feel like it could help some. For example, v1.1 lacks some options that show up in the v0.12 "Maven/Lifecycle Mapping" dialog in the project properties (in particular related to what goals get built as a result of "clean"s or resource changes). What can/should I infer from that? Also, in v0.12, the "Maven Console" window shows me a lot of stuff that I assume is telling me what the m2e builder is doing (or at least that it's doing something). In contrast, the v1.1 "Maven Console" window never seems to have anything in it. So I don't ever have a sense of when it's doing something and what it's doing. Thanks for your help. Nat On Wed, Aug 15, 2012 at 7:28 PM, Igor Fedorenko <[email protected] <mailto:[email protected]>> wrote: In short, antrun-plugin is not supported by m2e (and never was, btw). You need to reimplement properties file generation logic in eclipse-friendly manner. I assume you already saw m2e wiki on the subject [1], but have a read if you did not. I can provide more detailed explanation of how m2e builder actually works, but this is more a developer subject, so let me know on m2e-dev if you want to know nitty-gritty of it. [1] http://wiki.eclipse.org/M2E___plugin_execution_not_covered <http://wiki.eclipse.org/M2E_plugin_execution_not_covered> -- Regards, Igor On 12-08-15 5:47 PM, Nathaniel Mishkin wrote: I'm attempting to convert a large and complex multi-module project environment from m2eclipse (v0.12) to m2e (v1.1). I have things pretty much working well but things are getting messed up by what I assume are differences between the way the Maven Project Builder works in v0.12 vs. v1.1. In particular, one of my projects uses the /maven-antrun-plugin/ to do some stuff the net effect of which is to leave some Java properties files somewhere deep under /target/classes/. The problem arises in cases where the Eclipse "clean" operation occurs. In v0.12 this seems to be OK because it looks like the the Maven Project Builder does enough of a “real” Maven build to recreate those files. In contrast, in v1.1, well, I don’t know quite what the m2e Maven Project Builder does, but in any case I’ve configured m2e to ignore the /maven-antrun-plugin/ (which I need to do to make m2e not complain) so the Java properties file doesn’t get recreated and the launch of my application fails because those files are required. I can go back and do a Maven command line build, which fixes things until the next Eclipse "clean". Not pretty. Any suggestions for a good way of dealing with this situation? Any general background on the behavior of the Maven Project Builder would be helpful too/instead. Thanks. Nat _________________________________________________ m2e-users mailing list [email protected] <mailto:[email protected]> https://dev.eclipse.org/__mailman/listinfo/m2e-users <https://dev.eclipse.org/mailman/listinfo/m2e-users> _________________________________________________ m2e-users mailing list [email protected] <mailto:[email protected]> https://dev.eclipse.org/__mailman/listinfo/m2e-users <https://dev.eclipse.org/mailman/listinfo/m2e-users> _______________________________________________ m2e-users mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/m2e-users
_______________________________________________ m2e-users mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/m2e-users
