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

[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?

From: Gunnar Wagenknecht <gunnar@xxxxxxxxxxxxxxx>
Date: Sun, 5 Feb 2023 11:28:09 +0100
Delivered-to: mylyn-dev@xxxxxxxxxxx
List-archive: <https://www.eclipse.org/mailman/private/mylyn-dev/>
List-help: <mailto:mylyn-dev-request@eclipse.org?subject=help>
List-subscribe: <https://www.eclipse.org/mailman/listinfo/mylyn-dev>, <mailto:mylyn-dev-request@eclipse.org?subject=subscribe>
List-unsubscribe: <https://www.eclipse.org/mailman/options/mylyn-dev>, <mailto:mylyn-dev-request@eclipse.org?subject=unsubscribe>

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/

Follow-Ups:
- Re: [mylyn-dev] Do we really need the .classpath/.project/.settings files in git?
  - From: George Lindholm

References:
- [mylyn-dev] Do we really need the .classpath/.project/.settings files in git?
  - From: George Lindholm
- Re: [mylyn-dev] Do we really need the .classpath/.project/.settings files in git?
  - From: Frank Becker (Eclipse)
- Re: [mylyn-dev] Do we really need the .classpath/.project/.settings files in git?
  - From: George Lindholm

Prev by Date: Re: [mylyn-dev] Do we really need the .classpath/.project/.settings files in git?
Next by Date: [mylyn-dev] Mylyn Builds documentation?
Previous by thread: Re: [mylyn-dev] Do we really need the .classpath/.project/.settings files in git?
Next by thread: Re: [mylyn-dev] Do we really need the .classpath/.project/.settings files in git?
Index(es):
- Date
- Thread

Breadcrumbs