>
> artifact descriptor for
> org.apache.hadoop:hadoop-build-tools:jar:3.3.9-SNAPSHOT: Could not transfer
> artifact org.apache.hadoop:hadoop-build-tools:pom:3.3.9-SNAPSHOT from/to
> maven-default-http-blocker (http://0.0.0.0/): Blocked mirror for
> repositories: [apache.snapshots (http://repositor
Yes I am aware of that and so I was confused because we do have snapshot
repository defined in Ozone's pom.xml.
https://github.com/apache/ozone/blame/master/pom.xml#L86
Does it define where Ozone upload the snapshots rather than defining where
to download dependency snapshots? I'll check this out
Hi Wei-Chiu,
It says the snapshot maven repo is blocked from your logs:
Blocked mirror for
> repositories: [apache.snapshots (http://repository.apache.org/snapshots,
> default, snapshots)] -> [Help 1]
>
I believe It is caused by using insecure http:// maven repo by default:
https://stackove
Hi developers,
Is there a way to update the hadoop dependency to a SNAPSHOT version? I
have a draft PR that relies on a new Hadoop feature
https://github.com/apache/ozone/pull/4825/files#diff-9c5fb3d1b7e3b0f54bc5c4182965c4fe1f9023d449017cece3005d3f90e8e4d8
So instead of hadoop 3.3.5, i have it con
Dear developers,
I would like to inform you that after we started to implement the rootCA
certificate rotation piece for the certificate rotation feature, we got to a
conclusion that we are able to do all the changes without disrupting the
code
on the master branch.
So for the sake of simplicity,
On the certificate rotation front, we are approaching a major milestone,
with
all services becoming capable of rotating their certificates without
service disruption including the rootCA certificate as well.
We also have resolved a few things around the need for the primordial node,
we can not get
