#1880: Allow reset of installed plugins when launching IDE in force mode#1891
#1880: Allow reset of installed plugins when launching IDE in force mode#1891areinicke wants to merge 16 commits into
Conversation
Coverage Report for CI Build 25721470472Coverage increased (+0.04%) to 70.666%Details
Uncovered ChangesNo uncovered changes found. Coverage Regressions132 previously-covered lines in 3 files lost coverage.
Coverage Stats💛 - Coveralls |
|
I tested the -f option with vscode and intellij. With vscode, everything works and looks good! With intellij i get this one always (not sure if this comes from your changes, i guess not...): Also happens without the -f option, so i guess this is another error...your changes look good! |
|
Yeah. The PlantUML extension seems to be broken. But like you said, this has nothing to do with my changes. |
hohwille
left a comment
There was a problem hiding this comment.
@areinicke thank you for your story idea and this PR implementing it. Great that you also found the perfect spot to document the new feature. 👍
I do have one concern and would like to suggest some improvement via my review comment. Please have a look and consider a small upgrade of this PR. Thanks.
…ps://github.com/areinicke/IDEasy into feature/1880-reset-ide-plugins-when-using-force
|
I have re-factored the code to no longer use the force mode for plugin reset but a dedicated feature flag ( |
satorus
left a comment
There was a problem hiding this comment.
The flag works and all plugins are getting reinstalled as far as i can see, good job!
The only thing would be that there is not really any indication for the user that the flag does something...the only log output that all plugins are being deleted is on log level DEBUG, which is not usually shown to the user.
Maybe it would be good to add some console output indicating that the flag did something.
This PR fixes #1880
Implemented changes:
Checklist for this PR
Make sure everything is checked before merging this PR. For further info please also see
our DoD.
mvn clean testlocally all tests pass and build is successful#«issue-id»: «brief summary»(e.g.#921: fixed setup.bat). If no issue ID exists, title only.In Progressand assigned to you or there is no issue (might happen for very small PRs)with
internal