Bug 529607

Summary:	When opening a pom file from a non-m2e project with m2e editor, propose to configure project
Product:	z_Archived	Reporter:	Mickael Istria <mistria>
Component:	m2e	Assignee:	Project Inbox <m2e.core-inbox>
Status:	NEW ---	QA Contact:
Severity:	enhancement
Priority:	P3	CC:	gautier.desaintmartinlacaze
Version:	unspecified	Keywords:	usability
Target Milestone:	---
Hardware:	All
OS:	All
Whiteboard:

Description Mickael Istria

2018-01-10 03:13:46 EST

As a Java developer
When I open a pom.xml file in Eclipse IDE from a project I already have in workspace.
I'd expect m2e to configure the project at best to be usable.
I get the editor but the project is not configured.

In this case, I'd love to see a pop-up: "Project <blah> is not configured to support Maven. Do you want to configure it now?" that would drive me to most appropriate UI to configure the project.

Comment 1 Mickael Istria

2021-03-30 05:29:36 EDT

Eclipse m2e is moving away from this bugs.eclipse.org issue tracker to https://github.com/eclipse-m2e/m2e-core/issues/ instead. If this issue is relevant to you, your action is required.
0. Verify this issue is still happening with latest Eclipse Platform and m2e release
  if issue has disappeared, please change status of this issue to "CLOSED WORKFORME" with some details about your testing environment and how you did verify the issue; and you're done
  if issue is still present when latest release:
* Create a new issue at https://github.com/eclipse-m2e/m2e-core/issues/
  ** Use as title in GitHub the title of this Bugzilla ticket (may include the bug number or not, at your own convenience)
  ** In the GitHub description, start with a link to this bugzilla ticket
  ** Optionally add new content to the description if it can helps towards resolution
  ** Submit GitHub issue
* Update bugzilla ticket
  ** Add to "See also" property (up right column) the link to the newly created GitHub issue
  ** Add a comment "Migrated to <link-to-newly-created-GitHub-issue>"
  ** Set status as CLOSED MOVED
  ** Submit

All issues that remain open will be automatically closed next week or so. Then the m2e component for m2e will be made read-only.

Comment 2 Mickael Istria

2021-03-30 05:35:02 EDT

Eclipse m2e is moving away from this bugs.eclipse.org issue tracker to https://github.com/eclipse-m2e/m2e-core/issues/ instead. If this issue is relevant to you, your action is required.
0. Verify this issue is still happening with latest Eclipse Platform and m2e release
  if issue has disappeared, please change status of this issue to "CLOSED WORKFORME" with some details about your testing environment and how you did verify the issue; and you're done
  if issue is still present when latest release:
* Create a new issue at https://github.com/eclipse-m2e/m2e-core/issues/
  ** Use as title in GitHub the title of this Bugzilla ticket (may include the bug number or not, at your own convenience)
  ** In the GitHub description, start with a link to this bugzilla ticket
  ** Optionally add new content to the description if it can helps towards resolution
  ** Submit GitHub issue
* Update bugzilla ticket
  ** Add to "See also" property (up right column) the link to the newly created GitHub issue
  ** Add a comment "Migrated to <link-to-newly-created-GitHub-issue>"
  ** Set status as CLOSED MOVED
  ** Submit

All issues that remain open will be automatically closed next week or so. Then the m2e component for m2e will be made read-only.

Comment 3 Denis Roy

2021-04-19 13:25:35 EDT

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