Fixed ConcurrentModificationException on a map and tweeked some options.
Do you have a stack trace of the ConcurrentModificationException?
I had one, but did not record it, pointing on the second call to it.next(), denoting the map change due to the put() on it; the proposed and tested fix is to use an additional map ca2.
Le sam. 12 juil. 2025 à 11:17, Olivier Lamy @.***> a écrit :
olamy left a comment (codehaus-plexus/plexus-compiler#443) https://github.com/codehaus-plexus/plexus-compiler/pull/443#issuecomment-3064980431
Do you have a stack trace of the ConcurrentModificationException?
— Reply to this email directly, view it on GitHub https://github.com/codehaus-plexus/plexus-compiler/pull/443#issuecomment-3064980431, or unsubscribe https://github.com/notifications/unsubscribe-auth/AFQZRCZPKINQOZYDFJBRWVT3IDHBLAVCNFSM6AAAAACBDR3KUSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTANRUHE4DANBTGE . You are receiving this because you authored the thread.Message ID: @.***>
I added a commit to fix erroneous excludes management.
Do you have a stack trace of the ConcurrentModificationException?
You should get one easily with:
<compilerArgs>
<arg>-nologo:true</arg>
<arg>-nowarn:0414</arg>
<arg>-utf8output:true</arg>
<arg>-target:exe</arg>
<arg>-out:${project.artifactId}.exe</arg>
</compilerArgs>