Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 335710 - Improve handling of project configuration update
Summary: Improve handling of project configuration update
Status: CLOSED FIXED
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: m2e (show other bugs)
Version: unspecified   Edit
Hardware: PC Mac OS X - Carbon (unsup.)
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on: 335719 335720
Blocks:
  Show dependency tree
 
Reported: 2011-01-28 12:35 EST by Pascal Rapicault CLA
Modified: 2021-04-19 13:23 EDT (History)
1 user (show)

See Also:

Attachments
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 Pascal Rapicault CLA 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 CLA 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 CLA 2021-04-19 13:23:52 EDT 
Moved to https://github.com/eclipse-m2e/m2e-core/issues/