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

Bug 353565

Summary: Using a non-embedded Maven breaks launch configs
Product: z_Archived Reporter: Aaron Digulla <digulla>
Component: m2eAssignee: Project Inbox <m2e.core-inbox>
Status: CLOSED DUPLICATE QA Contact:
Severity: normal    
Priority: P3 CC: igor
Version: unspecified   
Target Milestone: ---   
Hardware: All   
OS: All   
Whiteboard:

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/