Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 334462 - Trim versions covered by dependencyManagement when adding dependencies
Summary: Trim versions covered by dependencyManagement when adding dependencies
Status: RESOLVED FIXED
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: m2e (show other bugs)
Version: unspecified   Edit
Hardware: Macintosh Mac OS X - Carbon (unsup.)
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-01-15 14:06 EST by benson margulies CLA
Modified: 2021-04-19 13:22 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 benson margulies CLA 2011-01-15 14:06:09 EST 
Build Identifier: 20100917-0705

If I use the POM editor to add a dependency, and the dependency is included in dependencyManagement or a parent, m2e still adds the explicit version number to the POM.

Reproducible: Always

Steps to Reproduce:
1. make parent/child project set with dependency management in parent
2. add dependency to child
3. observe results
Comment 1 Sahoo CLA 2011-01-23 12:42:16 EST 
When can I expect this bug to be fixed?
Comment 2 Milos Kleint CLA 2011-01-27 08:43:33 EST 
both adding dependencies from the form editor and xml editor have been rewamped. please see:
http://www.sonatype.com/people/2011/01/inserting-artifacts-in-the-m2eclipse-pom-editor/

consider this fixed, please reopen if you disagree.
Comment 3 Denis Roy CLA 2021-04-19 13:22:16 EDT 
Moved to https://github.com/eclipse-m2e/m2e-core/issues/