Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 335719 - Tell the user when the project configuration is not up-to-date
Summary: Tell the user when the project configuration is not up-to-date
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 normal (vote)
Target Milestone: ---   Edit
Assignee: Igor Fedorenko CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 335710
  Show dependency tree
 
Reported: 2011-01-28 13:15 EST by Pascal Rapicault CLA
Modified: 2021-04-19 13:22 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Pascal Rapicault CLA 2011-01-28 13:15:23 EST
As a first improvement toward bug #335710, we need to be able to detect is the project configuration is up-to-date or not, and show a warning or some sort of marker.
Ideally a quickfix should be associated with it.
Comment 1 Igor Fedorenko CLA 2011-02-04 21:36:20 EST
Implemented. m2e will add error markers to indicate that workspace project configuration and pom.xml are out of sync. Default implementation compares lifecycle mapping metadata and configuration of interesting mojo executions to determine if project configuration requires update or not. Although I expect the default behaviour to be good enough in vast majority of cases, m2e extensions can provide alternative configuration comparison logic both at ILifecycleMapping and AbstractProjectConfigurator layer.
Comment 2 Igor Fedorenko CLA 2011-02-07 19:48:07 EST
To be more specific, m2e expects Xpp3Dom to be serializable and this has been added in plexus-utils 2.0.6-SNAPSHOT
Comment 3 Pascal Rapicault CLA 2011-02-28 14:46:32 EST
I have seen this when changing
Comment 4 Denis Roy CLA 2021-04-19 13:22:57 EDT
Moved to https://github.com/eclipse-m2e/m2e-core/issues/