-
Notifications
You must be signed in to change notification settings - Fork 4
fix: 🐛 switch to sequential deletion #1809
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
Conversation
|
🤖 Hey ! The @cpn-console/nexus-plugin (v2.3.1) package already exists on npm but the source code has changed, you should consider updating the package version. The version update warning should be ignored in the case of modifications that do not affect the code once it has been built, such as code formatting, etc... |
|
🤖 Hey ! The security scan report for the current pull request is available here. |
|
🤖 Hey ! A preview of the application is available at : https://console-pr-1809.sdid-hp.cpin.numerique-interieur.com Please be patient, deployment may take a few minutes. |
StephaneTrebel
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Une question qui relève plus du nitpick pour être honnête, donc à toi de voir.
Dans l'ensemble LGTM
To avoid ConcurrentModificationException
4bd41dc to
297706b
Compare
|

0 New Issues
0 Fixed Issues
0 Accepted Issues
No data about coverage (73.70% Estimated after merge)
Issues liées
Issues numéro:
Quel est le comportement actuel ?
When deleting a project using Nexus Maven plugin, we are facing the following error.
Nexus logs show
java.util.ConcurrentModificationException.Quel est le nouveau comportement ?
Avoid concurrent modification exception by sequentializing deletion.
Cette PR introduit-elle un breaking change ?
No.
Autres informations
No.