Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [mylyn-dev] Do we really need the .classpath/.project/.settings files in git?

That’s the hard part. We export settings and import them. I wish there was a better way, as in moving content out of .project and .settings – I had a bug open on ECLIPSE for this in general that never got fixed.

 

From: Frank Becker (Eclipse) <eclipse@xxxxxxxxxxxxxxx>
Sent: Tuesday, April 11, 2023 1:43 AM
To: rsbecker@xxxxxxxxxxxxx; Mylyn developer discussions <mylyn-dev@xxxxxxxxxxx>
Subject: Re: [mylyn-dev] Do we really need the .classpath/.project/.settings files in git?

 

The filteredResource is used to avoid that a project showed twice in the PackageExplorer View. The filter removes the subfolder of the root repository.

 

If you do not use the .settings you can not set project specific code style like formatting, …

 

How would you manage that all contributors use the requested same settings?

 

Regards

Frank 



Am 09.04.2023 um 20:25 schrieb <rsbecker@xxxxxxxxxxxxx> <rsbecker@xxxxxxxxxxxxx>:

 

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:

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

 

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

 


Back to the top