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
Currently if the version of my project increments from 1.0 to 1.1 in a multi-module maven project, there are simply an entire set of new projects created with the new version, and the last versions do not get deleted. I would like to still show the actual version in dependency track, so manually setting it to "development" or something similar isn't a good solution for me.
I would also not like to just delete the old project and create a new one because then I lose all of the history that was tied to that project, as far as vulnerabilities go.
A new configuration to allow me to just enable keepNewestVersionOnly and that causes the verison to update, would be perfect.
The text was updated successfully, but these errors were encountered:
Currently if the version of my project increments from 1.0 to 1.1 in a multi-module maven project, there are simply an entire set of new projects created with the new version, and the last versions do not get deleted. I would like to still show the actual version in dependency track, so manually setting it to "development" or something similar isn't a good solution for me.
I would also not like to just delete the old project and create a new one because then I lose all of the history that was tied to that project, as far as vulnerabilities go.
A new configuration to allow me to just enable keepNewestVersionOnly and that causes the verison to update, would be perfect.
The text was updated successfully, but these errors were encountered: