Community
Participate
Working Groups
Created attachment 189983 [details] screenshot of the problem In the dependency management page of the editor, I would to have the variable to be resolved. See screenshot.
I think it is important to know when properties are used and when version is hardcoded, so I think we need to show both ${variable} and variable value somehow.
the problem I can see is that the resolved version doesn't need to express the actual version in the view. Let's take this example: you have the dependency defined with ${aaa.version} expression. the resolved version says 1.2. But there are situations where changing either the version *or* the property has no influence on the resolved value. -> eg. when the resolved value is taken from activated profile which we don't show in the view. The profile can define either the dependency or just the property. Another aspect is how to show the values, let's see what we already show. 1. optionally the groupId (off by default) 2. artifactId, version 3. optionally ( show if present) scope, classifier and type of the dependency. 4. the managed version at the end (if indeed managed) Given that we show 2 columns on the page, it happens frequently that even the current display is not entirely visible and user is forced to scroll horizontally. (Now that I mentioned it I believe the view is broken because one cannot scroll horizontally at all)
closing old/stale bugreports
Moved to https://github.com/eclipse-m2e/m2e-core/issues/
