[
https://issues.apache.org/jira/browse/RATIS-672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16936229#comment-16936229
]
Clay B. commented on RATIS-672:
-------------------------------
[~elserj] sorry for the long delay on this. There are two philosophies:
# Should we track upstream projects, moving to track upstream projects (with
checksum's somehow pulled from a different location)
# Should we pin to fixed versions and provide an easy getting started path and
a known working set of dependencies
I picked the second option in the latest rebase and push. It should now be
checksum verifying all downloads as should have been done originally.
> Vagrant test's Maven 404's
> --------------------------
>
> Key: RATIS-672
> URL: https://issues.apache.org/jira/browse/RATIS-672
> Project: Ratis
> Issue Type: Improvement
> Components: test
> Reporter: Clay B.
> Assignee: Clay B.
> Priority: Trivial
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The Vagrant tests are
> [pointing|https://github.com/apache/incubator-ratis/blob/35838f032a4096d78843130fa1435bcddf5ce961/dev-support/vagrant/Vagrantfile#L92]
> to a specific mirror and a URL which broke with the new Maven 3.6.x release.
> We should point to an {{archive.apache.org}} URL if I understand correctly.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
