Hmm. I guess my thought would be that we would have a fixed number of
"slots" (i.e. executors on a single node with associated .m2
directories). Then we wouldn't clear each .m2 in between runs, but we
would ensure that only one slot at a time had access to each
directory.
In that case, build tim
Akira AJISAKA created HADOOP-11615:
--
Summary: Remove MRv1-specific terms from ServiceLevelAuth.md
Key: HADOOP-11615
URL: https://issues.apache.org/jira/browse/HADOOP-11615
Project: Hadoop Common
Akira AJISAKA created HADOOP-11614:
--
Summary: Remove httpclient dependency from hadoop-openstack
Key: HADOOP-11614
URL: https://issues.apache.org/jira/browse/HADOOP-11614
Project: Hadoop Common
Akira AJISAKA created HADOOP-11613:
--
Summary: Remove httpclient dependency from hadoop-azure
Key: HADOOP-11613
URL: https://issues.apache.org/jira/browse/HADOOP-11613
Project: Hadoop Common
Robert Kanter created HADOOP-11612:
--
Summary: Workaround for Curator's ChildReaper requiring Guava 15+
Key: HADOOP-11612
URL: https://issues.apache.org/jira/browse/HADOOP-11612
Project: Hadoop Common
[
https://issues.apache.org/jira/browse/HADOOP-11611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Colin Patrick McCabe resolved HADOOP-11611.
---
Resolution: Fixed
wrong project
> fix TestHTracedRESTReceiver unit test fai
Colin Patrick McCabe created HADOOP-11611:
-
Summary: fix TestHTracedRESTReceiver unit test failures
Key: HADOOP-11611
URL: https://issues.apache.org/jira/browse/HADOOP-11611
Project: Hadoop Com
I¹m pretty sure there is no guarantee of isolation on a shared
.m2/repository directory for multiple concurrent Maven processes. I¹ve
had a theory for a while that one build running ³mvm install² can
overwrite the snapshot artifact that was just installed by another
concurrent build. This can cre
