You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Dependency-Track displays a yellow (warning) icon when a component is not the latest version. This icon is also displayed for a snapshot version of a component that is more recent than the "latest version"
Steps to Reproduce:
This should be easy to reproduce by uploading a BOM from a feature/dev branch of a multi-module maven project... the modules should all then be snapshot versions that will have a later version number than the latest release for the project.
Expected Behavior:
When latest > release, then do not indicate that the component is out of date. Indicate something else.
Ideally I would like to see an entirely different icon displayed. Per #311... different colour and different shape.
If this could be applied to snapshots generically then it would also capture a use case that I have seen: where project X has component X.Y that is used in project Z. A developer makes changes to X.Y and then "tries out" the snapshot in project Z (possibly X has rubbish tests and Z has excellent tests). Then they do a release of Z forgetting to include a release version of X.Y. Having a unique "version status" icon and being able to sort by "version status" (logged as #322) would make it easy to see when a project has this kind of problem.
Environment:
Dependency-Track Version: 4.6.1 (although I tested using 4.7 SNAPHOT due to authentication fix).
Client Browser: N/A
Client O/S: N/A
The text was updated successfully, but these errors were encountered:
Current Behavior:
Dependency-Track displays a yellow (warning) icon when a component is not the latest version. This icon is also displayed for a snapshot version of a component that is more recent than the "latest version"
Steps to Reproduce:
This should be easy to reproduce by uploading a BOM from a feature/dev branch of a multi-module maven project... the modules should all then be snapshot versions that will have a later version number than the latest release for the project.
Expected Behavior:
When latest > release, then do not indicate that the component is out of date. Indicate something else.
Ideally I would like to see an entirely different icon displayed. Per #311... different colour and different shape.
If this could be applied to snapshots generically then it would also capture a use case that I have seen: where project X has component X.Y that is used in project Z. A developer makes changes to X.Y and then "tries out" the snapshot in project Z (possibly X has rubbish tests and Z has excellent tests). Then they do a release of Z forgetting to include a release version of X.Y. Having a unique "version status" icon and being able to sort by "version status" (logged as #322) would make it easy to see when a project has this kind of problem.
Environment:
The text was updated successfully, but these errors were encountered: