Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 345713 - Update project configuration restores quickfixed groupid/version in modules
Summary: Update project configuration restores quickfixed groupid/version in modules
Status: CLOSED INVALID
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: m2e (show other bugs)
Version: unspecified   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-05-13 06:27 EDT by Fred Bricon CLA
Modified: 2021-04-19 13:27 EDT (History)
3 users (show)

See Also:

Attachments
Test projects demonstrating the bug (1.24 KB, application/zip)
2011-05-13 06:27 EDT, Fred Bricon 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 Fred Bricon CLA 2011-05-13 06:27:08 EDT 
Created attachment 195575 [details]
Test projects demonstrating the bug

Take some module projects duplicating their parent's groupId and version.
Apply quick fix to "GroupId is duplicate of parent groupId" and "Version is duplicate of parent version", the groupId and version are deleted as expected (you can check the pom.xml and then close it)
Now if you update the project configuration of either the modules or their parent, the groupId and version are restored in the modules pom. Warning markers reappear.
Deleting the groupId and version by hand fixes the issue.

Seems a stale representation of the model is kept in memory, after the quickfix.

You can check the issue by importing the attached projects.
Comment 1 Barrie Treloar CLA 2012-07-11 03:48:42 EDT 
Still effects 1.1.0

I dont believe the Quick Fix actually fixes the problem.
It is probably updating the in memory copy.

SVN status icons DO NOT change after applying the quick fix, and a Team > Sync shows the local copy is up to date.

Manually removing the groupId fixes the warning AND if you then do Maven > Update Project... the groupId does not get incorrectly put back.
Comment 2 Igor Fedorenko CLA 2013-09-28 23:32:47 EDT 
closing old/stale bugreport
Comment 3 Denis Roy CLA 2021-04-19 13:27:07 EDT 
Moved to https://github.com/eclipse-m2e/m2e-core/issues/