I think I've found the source of the issue. We are using assert-core on our fork of the repository, which is attempting to pull in junit-5.4.0. junit-5.4.0 doesn't seem to be published on either of the https repositories, so ant tries to hit the http as a backup and then fails with the error below.
It's curious that Junit was published to the http but not https repository. Either way, thanks for the assistance in debugging! On Wed, Jan 15, 2020 at 8:19 PM Leon Zaruvinsky <lzaruvin...@palantir.com.invalid> wrote: > I agree that something feels wonky on the Circle container. I was able to > successfully build locally. > > I SSHed into the container, cleared out .m2/repository and still can't get > it to build. Using ant 1.10.7 with environment: > > openjdk version "1.8.0_222" > OpenJDK Runtime Environment (build 1.8.0_222-8u222-b10-1~deb9u1-b10) > OpenJDK 64-Bit Server VM (build 25.222-b10, mixed mode) > > On 1/15/20, 7:14 PM, "Michael Shuler" <mich...@pbandjelly.org> wrote: > > I just did a quick `rm -r ~/.m2/repository/` so the build would > download > everything, and with 2.2.14 tag + 63ff65a8dd, the build succeeded for > me > fine, pulling everything from https. Not sure where to go, unless the > circleci container is somehow contaminated with http cached data. > > Michael > > On 1/15/20 6:05 PM, Michael Shuler wrote: > > Bleh, sorry, you updated those, right. > > > > I don't see any other related commits to build.xml nor > > build.properties.default.. Some elderly sub-dependent that has an > http > > URL in it, perhaps? > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org > For additional commands, e-mail: user-h...@cassandra.apache.org > > > >
