Re: [mylyn-dev] Do we really need the .classpath/.project/.settings file

[George Lindholm <javadev@xxxxxxxxxxxx>]

    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:

On Feb 5, 2023, at 08:51, George Lindholm <javadev@xxxxxxxxxxxx> 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.

-Gunnar

-- 
Gunnar Wagenknecht
gunnar@xxxxxxxxxxxxxxx, http://guw.io/

_______________________________________________
mylyn-dev mailing list
mylyn-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/mylyn-dev