You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It looks like the current domain referenced in pom.xml for Mesosphere, downloads.mesosphere.com no longer resolves in DNS. Its predecessor, downloads.mesosphere.io, also no longer resolves. Does anyone know if there's a replacement Maven location available? Alternatively, if there's a location we can download the Mesosphere Maven file tree from and push to our own private area on S3, that would work, as well. As it stands, Chronos won't currently build in Maven due to this dependency failure. If folks are aware of another way to get it building (such as pointing to the upstream repositories directly), we'd also be open to using that.
It looks like the current domain referenced in
pom.xml
for Mesosphere,downloads.mesosphere.com
no longer resolves in DNS. Its predecessor,downloads.mesosphere.io
, also no longer resolves. Does anyone know if there's a replacement Maven location available? Alternatively, if there's a location we can download the Mesosphere Maven file tree from and push to our own private area on S3, that would work, as well. As it stands, Chronos won't currently build in Maven due to this dependency failure. If folks are aware of another way to get it building (such as pointing to the upstream repositories directly), we'd also be open to using that.I believe the impacted dependencies are Chaos and mesos-utils
The text was updated successfully, but these errors were encountered: