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

Bug 339541

Summary:	m2e-wtp configuration is not enabled after install-during-import
Product:	z_Archived	Reporter:	Igor Fedorenko <igor>
Component:	m2e	Assignee:	Matthew Piggott <matthew>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	P3	CC:	matthew, pascal
Version:	unspecified
Target Milestone:	---
Hardware:	PC
OS:	Linux
Whiteboard:

Description Igor Fedorenko

2011-03-10 10:51:22 EST

Steps to reproduce

* start with clean eclipse for java developers with recent m2e 0.13.0
* import a webapp project using Import Existing Maven Projects wizards
* allow m2e to install m2e-wtp as part of import flow
* allow m2e to restart eclipse after import and installation have finished

Expected result - imported project has proper wtp configuration

Observed behaviour - the project does not have wtp configuration.

Workaround - right-click and do Maven->UpdateProjectConfiguration

Implementation notes. Internally, m2e relies on error markers to determine configuration of which projects should be updated after installation and restart. In case of webapp project, however, there are no error markers because m2e provides default basic mapping for packaging=war.

Comment 1 Matthew Piggott

2011-03-10 13:34:36 EST

http://git.eclipse.org/c/m2e/m2e-core.git/commit/?id=88c1c7315bd943ed990fb503cfcd8de69eb0b214

Comment 2 Igor Fedorenko

2011-03-10 14:34:58 EST

I verified the fix addresses the issue. I think this bugzilla can be resolved now.

Comment 3 Matthew Piggott

2011-03-10 15:11:02 EST

Flipping over.

Comment 4 Denis Roy

2021-04-19 13:23:56 EDT

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