Within Eclipse Kepler we are using org.eclipse.m2e.feature_1.4.0.20130601-0317
Going to try a fresh import again, maybe its because or the older version we use ... - Frank 2015-09-09 15:09 GMT+02:00 Fred Bricon <[email protected]>: > these files are automatically generated on maven project import, or > project update. > The only reason to keep them in your SCM is if you have customized them > and automatic import gives you a different result. > > I'm curious to know what kind of diff you see between imports. Also, what > version of m2e-wtp are you using? > > On Wed, Sep 9, 2015 at 8:32 AM, Frank Gasdorf <[email protected] > > wrote: > >> Hello everybody, >> >> we are using git as SCM and the following .setting files are committed >> initially: >> >> >> >> >> *.settings/org.eclipse.wst.common.component.settings/org.eclipse.wst.common.project.facet.core.xml* >> since we have workspace resolution for mvn modules activated we have the >> following scenario which drives us a bit crazy: >> * the first file gets updated every time a Developer imports a project >> that is referenced in pom.xml >> * git always mark this file as changed >> * some Developers just add, commit, and push these changes, while others >> know that the change are workspace specific and are not valid for others >> * some changes in pom.xml file (e.g. contextName) are relevant and >> settings file content updated by m2e correclty (maven --> update project... >> >> >> I'd like to get an impression how others handle this to avoid always "git >> checkout --" for .settings files before committing relevant changes to the >> project such as java files, etc >> >> I tried to use "--assume-unchanged" option in gitbut IMHO its not really >> an option because if others clone a repositorythey have to configure it >> again. On the other hand it can be hard to get updates from others in. >> >> In addition, the wst files are required to have a proper Eclipse project >> setup. Is it an option to generate these (Maven --> Uptate project ...) >> before or during "Import Maven project into Workspace". >> >> Looking forward to hear best practices from others >> >> In regards >> - Frank >> >> _______________________________________________ >> m2e-wtp-dev mailing list >> [email protected] >> To change your delivery options, retrieve your password, or unsubscribe >> from this list, visit >> https://dev.eclipse.org/mailman/listinfo/m2e-wtp-dev >> > > > > -- > "Have you tried turning it off and on again" - The IT Crowd > And if that fails, then http://goo.gl/tnBgH5 >
_______________________________________________ m2e-wtp-dev mailing list [email protected] To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/m2e-wtp-dev
