I have seen this too, when Mylyn was in use at my org. I usually keep .cproject, .gitignore, .gitmodules, and .project but not .settings. When .settings is included, we often will use git update-index --assume-unchanged .settings and .project to ignore changes after the initial project setup where we do not yet include Mylyn content. Hope this helps. From: mylyn-dev <mylyn-dev-bounces@xxxxxxxxxxx> On Behalf Of George Lindholm
Sent: Sunday, April 9, 2023 1:48 PM
To: mylyn-dev@xxxxxxxxxxx
Subject: Re: [mylyn-dev] Do we really need the .classpath/.project/.settings files in git? So what do I do about changes like this:
<filteredResources> <filter> <id>1672000970093</id> <name></name> <type>10</type> <matcher> <id>org.eclipse.ui.ide.multiFilter</id> <arguments>1.0-name-matches-false-false-org.eclipse.mylyn.*</arguments> </matcher> </filter> <filter> <id>1672000970100</id> <name></name> <type>10</type> <matcher> <id>org.eclipse.ui.ide.multiFilter</id> <arguments>1.0-name-matches-false-false-mylyn.*</arguments> </matcher> </filter> </filteredResources>
that keep appearing in the top level .project files?
George On 2023-02-05 02:28, Gunnar Wagenknecht wrote: My point is that those files are generated by maven when a project is imported
I've noticed that this can cause inconsistency among team members due to environment/system issues. Additionally, .settings such ad Eclipse code formatter and import organization are not manages by M2E AFAIK.
_______________________________________________ mylyn-dev mailing list mylyn-dev@xxxxxxxxxxx To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/mylyn-dev
|
