Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 339541 - m2e-wtp configuration is not enabled after install-during-import
Summary: m2e-wtp configuration is not enabled after install-during-import
Status: RESOLVED FIXED
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: Matthew Piggott CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-03-10 10:51 EST by Igor Fedorenko CLA
Modified: 2021-04-19 13:23 EDT (History)
2 users (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 Igor Fedorenko CLA 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 2 Igor Fedorenko CLA 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 CLA 2011-03-10 15:11:02 EST 
Flipping over.
Comment 4 Denis Roy CLA 2021-04-19 13:23:56 EDT 
Moved to https://github.com/eclipse-m2e/m2e-core/issues/