Re: [jbosstools-dev] [m2e-users] Automatic out-of-date configuration updates

Are there conditions under which we can know it's safe? If every Mojo execution has an associated connector or configuration in the POM to address its presence can we safely run the update? After going through the import process we encourage users to address any inconsistencies in the mappings between their Mojo executions and what M2Eclipse knows about them. So if this is done and we can deterministically know it's done would it be safe to just keep projects in sync, and if not how might address that? For example if I have a simple project with only a maven-compiler-plugin configuration and I change the source and target can the update be safely run? Does the connector know not to just execute if the required Java language level cannot be satisfied from the environment for example? And if it's not can that be reported in a way for the user to correct it? I can certainly understand how you might not want to run this with a bunch of random Mojo executions where you haven't spent the time to setup a mapping configuration, but if the user have we should deterministically know when we can run the update and do it automatically and correctly. This would definitely make for a much better user experience. On Nov 7, 2014, at 4:36 PM, Fred Bricon <fbricon(a)gmail.com&gt; wrote: Thanks, Jason ---------------------------------------------------------- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl http://twitter.com/takari_io --------------------------------------------------------- Selfish deeds are the shortest path to self destruction. -- The Seven Samuari, Akira Kurosawa