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
Maven Check does a great job of identifying outdated versions, but it would be incredibly helpful if it could also apply these updates automatically with an additional command-line parameter.
The text was updated successfully, but these errors were encountered:
Thank you for your feedback and the interest you have for Maven Check, it is really appreciated.
The goal of Maven Check is to help developers to keep their projects up-to-date, by informing them about a new version of dependencies. Most of the times bumping to a newer version have no effect on your project and is transparent, that feature would fit perfectly for that. But in rare cases, the dependency API or a behavior may change and impact your project. For that reason, I think it is a good practice to read the release note or the changelog each time before bumping a version and I discourage doing it blindly.
That said, having an option disabled by default as you described may be envisaged. Not that it would require a lot of work because sometimes versions are inherited from a property or a parent file. Should we update a parent file even if it is not in the current project directory where the command was run? I think it would not be possible to bump concatenated or runtime generated versions.
Maven Check does a great job of identifying outdated versions, but it would be incredibly helpful if it could also apply these updates automatically with an additional command-line parameter.
The text was updated successfully, but these errors were encountered: