343530 – pom.xml changes are ignored in some cases

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

Bug 343530 - pom.xml changes are ignored in some cases

Summary: pom.xml changes are ignored in some cases

Status:	RESOLVED FIXED

Alias:	None

Product:	z_Archived
Classification:	Eclipse Foundation
Component:	m2e (show other bugs)
Version:	unspecified
Hardware:	PC Linux

Importance:	P3 normal (vote)
Target Milestone:	---
Assignee:	Igor Fedorenko
QA Contact:

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2011-04-21 09:31 EDT by Igor Fedorenko
Modified:	2021-04-19 13:23 EDT (History)
CC List:	0 users

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 Igor Fedorenko

2011-04-21 09:31:01 EDT

Looks like there are cases when MavenBuilder does not refresh MavenProjectFacade instance after corresponding pom.xml has been modified and saved. Not always reproducible but from code review it appears that if ProjectRegistryManager.refresh could not read MavenProject for whatever reason, MavenBuilder never attempts to re-read it. 

A workaround is to force update from project right-click menu.

Comment 1 Igor Fedorenko

2011-04-21 12:04:33 EDT

Fixed.

http://git.eclipse.org/c/m2e/m2e-core.git/commit/?id=8e465f10e2e4739b7a6fe8ebd1ed117ef8435073

https://github.com/sonatype/m2e-core-tests/commit/1f6a186b6919f280a8699d078707a814e0bb47e6

Also opened separate bug 343568 and corresponding root-cause http://jira.codehaus.org/browse/MNG-5073, which explain why project facade is null quite often.

Comment 2 Denis Roy

2021-04-19 13:23:19 EDT

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