Fred,
I haven't looked yet, but the code defend against the user making repeated edits to the POMs? Basically preventing against endless builds? I'm certainly in favour of trying the strategy and being perfect is the enemy of the good, but it would still be nice to keep in mind keeping the workspace build from spiraling out of control.
Is the maven-compiler-plugin our worst case scenario? Something that triggers full workspace build? We have any other connectors that require full-scale workspace rebuild? At least in the project setup that I have the maven-compiler-plugin doesn't change in practice but the configuration of other plugins will frequently and this would be a nice addition to help users. Hi,
FYI, I whipped up a small plugin that automatically update out-of-date project configuration, under our JBoss Tools Playground repo [1].
I'm not sure if it's completely safe to use. There's no preference to (de)activate it -yet-. The plugin is set to start on workspace startup for now, which isn't ideal, but if you deactivate it from Preferences > Startup and Shutdown and restart the workspace, it should be inactive. It's, most probably, sub-optimally implemented, but it worked on the small set of projects I tried.
p2 site to install it from is at [2]. Feel free to try it and give some feedback. Then we can discuss what to do with it, wrt [3]. [3] https://bugs.eclipse.org/bugs/show_bug.cgi?id=335720
Fred
-- "Have you tried turning it off and on again" - The IT Crowd
_______________________________________________ m2e-users mailing list m2e-users@xxxxxxxxxxx To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/m2e-users
Thanks,
Jason
---------------------------------------------------------- Jason van Zyl Founder, Apache Maven
|