Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 353565 - Using a non-embedded Maven breaks launch configs
Summary: Using a non-embedded Maven breaks launch configs
Status: CLOSED DUPLICATE of bug 379012
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: m2e (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-08-02 07:55 EDT by Aaron Digulla CLA
Modified: 2021-04-19 13:22 EDT (History)
1 user (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 Aaron Digulla CLA 2011-08-02 07:55:46 EDT 
If I use an external Maven installation and select that in a Launch config, then the absolute path is added to the launch config. This breaks the launch config for everyone in the team because this path is often different (between Windows and Linux or between different users if Maven is installed in, say, $HOME).

Please allow to specify a virtual name for Maven installations which should be used in the .launch files instead of the absolute path.
Comment 1 Igor Fedorenko CLA 2012-05-21 11:05:46 EDT 

*** This bug has been marked as a duplicate of bug 379012 ***
Comment 2 Denis Roy CLA 2021-04-19 13:22:49 EDT 
Moved to https://github.com/eclipse-m2e/m2e-core/issues/