On Tuesday 15 January 2013 13:55:53 Martin Grigorov wrote: > On Tue, Jan 15, 2013 at 1:30 PM, Emond Papegaaij > > <[email protected]>wrote: > > I've synced all settings with core and added the new files (which probably > > only contain some defaults). I agree with Martin that settings file in the > > source tree make it difficult to maintain them, unfortunately m2e does not > > I'm didn't mean that. > I'm saying that I've seen updates to these files in the same commit with > some functional change without explanation what is changed in the settings, > so non-Eclipse users canntot follow up. > For Eclipse users it is easy - next time you load the project the new > settings are automatically applied.
That's because the files are part of the source tree. If the settings files for different IDEs are maintained in a separate project, it is much easier to track changes. These setting files are often changed without knowing. If they are maintained in a central place, these accidental changes will not be pushed to all other users immediately. > I think m2e and maven-eclipse-plugin manipulate different files in > .settings/** so this should not be a problem. No, they use the same settings. Both however do not change settings if not needed. m2e seems to update the settings to match the eclipse version. > > (yet) support importing settings from a maven artifact. Hopefully they add > > this some time.... > > I'm not sure what you talk about. > Maven's pom.xml doesn't contain any code style rules which can be consumed > by IDE plugins like m2e, maven-eclipse-plugin, ... If there is anything in > the pom.xml then it is something specific to m2e, m-e-p, ... but not > something generic. > M2E has something very ugly (IMO) - its lifecycle mapping from Maven phases > to Eclipse. I hope this will never go in Wicket pom.xml files now when you > move to m2e. At Topicus, we have a special maven plugin in our pom that instructs m2e (through lifecycle mapping) to copy the settings from a maven artifact. For m- e-p we use something similar, where the maven-eclipse-plugin is configured to copy these setting files. If you do not use eclipse, the plugin should not get in your way and you do not have the settings files. Best regards, Emond
