Hi Kristian, There had to be some kind of issue with collection if Karl made IdentityMap synchronized. Whatever collections are too open. As an example, this is not right and it is not right in multithreading either:
request.setArtifactDependencies( project.getDependencyArtifacts() ); //common instance shared now in two object where one can change the status of second These collections are internally modifiable, and that's I guess what Herve means in "but inside core: it's harder to define the limits of collaboration" https://github.com/apache/maven/pull/34#issuecomment-68425530 Who is setting and modifying is safe? Who is getting collection and modifying is safe? Where is the limit, which status of object is kept and which one is modified? This is not clear because the impl is too open inside of the core and therefore any object can change anything. Cheers Tibor -- View this message in context: http://maven.40175.n5.nabble.com/Maven-Commit-3b671d07340b002e13775883d09e7f7e0d9a3c49-tp5821660p5821915.html Sent from the Maven Developers mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
