Community
Participate
Working Groups
In the dependencies tab of the POM editor I click on Add and search for a dependency from the management section of the parent pom. The managed versions are displayed at the top of the result list, but adding one dependency also adds the version information to the POM, which should not be set, since the dependency is managed after all.
I believe this is the correct behaviour, because depending on unversioned artifacts is bad.
(In reply to comment #1) > I believe this is the correct behaviour, because depending on unversioned > artifacts is bad. Wouldn't that defeat the purpose of dependencyManagement? :) I will probably take a look this week and see if there is a good fix. I imagine we introduced the problem when we moved from the EMF model.
I've released a fix for this, still working on some tests http://git.eclipse.org/c/m2e/m2e-core.git/commit/?id=c0c5ddb0a296fafdededd4756289fc84824d65cf
Added tests for the three cases: unmanaged, managed, and overriding managed version
Moved to https://github.com/eclipse-m2e/m2e-core/issues/