Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 361099 - 'Check out Maven Projects from SCM' modifies .classpath and org.eclipse.core.resources.prefs without reason
Summary: 'Check out Maven Projects from SCM' modifies .classpath and org.eclipse.core....
Status: CLOSED DUPLICATE of bug 342709
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: m2e (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-10-17 04:01 EDT by Daniel Ebert CLA
Modified: 2021-04-19 13:23 EDT (History)
1 user (show)

See Also:

Attachments
screenshot1 (16.75 KB, image/png)
2011-10-17 04:02 EDT, Daniel Ebert CLA 		no flags Details
screenshot2 (23.32 KB, image/png)
2011-10-17 04:03 EDT, Daniel Ebert CLA 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Daniel Ebert CLA 2011-10-17 04:01:57 EDT 
Build Identifier: 20110916-0149

Its quite annoying to see outgoing changes the moment you just checked out a project. Would be ok, if there actually had been done something useful by the plugin.

One outgoing change is the .classpath. In Synchronize View it just disappears for realizing that there has been no change at all.

The other outgoing change, '/.settings/org.eclipse.core.resources.prefs', does not disappear, even though there has been made no useful change. Sadly though, the timestamp at the top of this file has been modified.

Refer to my screenshots to see what happened.

Reproducible: Always

Steps to Reproduce:
1. Import -> Check out Maven Projects from SCM -> choose a maven project

What i expected: Not outgoing changes for a newly checked out project
What i got: Some outgoing changes for no visible reasons.
Comment 1 Daniel Ebert CLA 2011-10-17 04:02:52 EDT 
Created attachment 205298 [details]
screenshot1
Comment 2 Daniel Ebert CLA 2011-10-17 04:03:15 EDT 
Created attachment 205299 [details]
screenshot2
Comment 3 Igor Fedorenko CLA 2011-10-17 09:24:07 EDT 
m2e does not directly manage neither of the two affected files so jdt and/or platforms is where the problem should be fixed. There are no plans to investigate a workaround in m2e, but I'll keep this bug open in case somebody provides a quality patch.

See also bug 342709, which improves handling of .prefs files for modern version control systems like GIT.
Comment 4 Daniel Ebert CLA 2011-10-17 09:44:37 EDT 

*** This bug has been marked as a duplicate of bug 342709 ***
Comment 5 Denis Roy CLA 2021-04-19 13:23:59 EDT 
Moved to https://github.com/eclipse-m2e/m2e-core/issues/