[
https://issues.apache.org/jira/browse/HADOOP-12025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14557502#comment-14557502
]
Allen Wittenauer commented on HADOOP-12025:
-------------------------------------------
Maven, as a caching technology, is fundamentally broken. It provides zero
locking. Which means that multiple maven repo operations being performed
simultaneously will stomp all over each other. So matter what tricks one can
play with the pom.xml, artifact naming, etc, it just takes one job doing a
dependency:purge-local-repository or replacing a jar while another maven
operation is running a unit tests to make everything go haywire.
So any coordination or external locking to prevent this from happening would
have be done for every single project that runs on the same set of hosts.
It's just easier to use docker to virtually mount different directories to
prevent this from happening. So while there is still a risk, it's
significantly reduced.
> test-patch.sh needs per-project, per-branch maven repos
> -------------------------------------------------------
>
> Key: HADOOP-12025
> URL: https://issues.apache.org/jira/browse/HADOOP-12025
> Project: Hadoop Common
> Issue Type: Test
> Reporter: Allen Wittenauer
>
> Follow-up from HADOOP-11933.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
