Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 335710

Summary:	Improve handling of project configuration update
Product:	z_Archived	Reporter:	Pascal Rapicault <pascal>
Component:	m2e	Assignee:	Project Inbox <m2e.core-inbox>
Status:	CLOSED FIXED	QA Contact:
Severity:	enhancement
Priority:	P3	CC:	igor
Version:	unspecified
Target Milestone:	---
Hardware:	PC
OS:	Mac OS X - Carbon (unsup.)
Whiteboard:
Bug Depends on:	335719, 335720
Bug Blocks:

Description Pascal Rapicault

2011-01-28 12:35:03 EST

Sometimes the configuration of the project goes out-of-sync and it is hard for the user to figure it out. We should strive to make the "refreshing" of the project configuration more automatic if possible.
There are several cases of interest:
- The user updates from the SCM
- The update changes the pom
- The parent pom (a snapshot) has changed

Comment 1 Igor Fedorenko

2011-08-01 01:18:56 EDT

m2e creates project level error markers when workspace configuration and pom.xml get out of sync. 

problems with fully automatic reconciliation of workspace and pom

* it may be executed at undesired times, i.e. when the user is in a middle of something and wants to "stick" with the current configuration.
* it may destroy manual workspace configuration, like custom classpath entries.

Comment 2 Denis Roy

2021-04-19 13:23:52 EDT

Moved to https://github.com/eclipse-m2e/m2e-core/issues/