-
1. Re: ConcurrentModificationException on Archive.delete()
alrubinger Apr 18, 2013 1:49 PM (in response to mathias.deshayes)I'll bet MemoryMapArchiveBase.removeNodeRecursively is removing a Node while still inside of an iteration.
Michal is opening a JIRA for it; thanks for the report.
-
3. Re: ConcurrentModificationException on Archive.delete()
mathias.deshayes Apr 19, 2013 5:25 AM (in response to alrubinger)Thanks Andrew.
I "manually" delete children before deleting the resources folder for the moment and it works.
-
4. Re: ConcurrentModificationException on Archive.delete()
smikloso Aug 1, 2013 2:14 PM (in response to alrubinger)Hi,
I would like to know if I am safe to use ShrinkWrap 1.1.3 in connection with Arquillian core 1.1.0.Final since this release of Arquillian uses ShrinkWrap 1.1.2 where this issue is not resolved (it is done in 1.1.3 AFAIK), right?
What is the best practice here? Should I use ShrinkWrap 1.1.3 and override dependencies of Arquillian Core or is there some workaround how to do this in the code?
-
5. Re: ConcurrentModificationException on Archive.delete()
mmatloka Aug 1, 2013 2:25 PM (in response to smikloso)Hi,
Yes, issue is resolved in 1.1.3. It would be the best to use ShrinkWrap 1.1.3 with Arquillian 1.1.0.Final simply by overriding via dependency management (shrinkwrap dep management before arquillian in pom).
-
6. Re: ConcurrentModificationException on Archive.delete()
alrubinger Aug 1, 2013 3:36 PM (in response to mmatloka)Note: Make sure you put the shrinkwrap-bom artifact in dependencyManagement in "import" scope to ensure that all modules get the versions overridden correctly
-
7. Re: ConcurrentModificationException on Archive.delete()
kpiwko Aug 2, 2013 3:13 AM (in response to alrubinger)Also make sure that you place shrinkwrap-bom before arquillian-bom or jboss-javaee-6.0-with-tools BOM in <dependencyManagement>