Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add a new configuration value of keepNewestVersionOnly or something similar #425

Open
loganankarbergmdu opened this issue Oct 24, 2024 · 0 comments

Comments

@loganankarbergmdu
Copy link

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant