Hi Greg, we do use our own repo as the primary mirror already. However, our own repo is using their repo to cache the artifacts we are using, so what we need to do is update our own repository to reflect their new url scheme (http instead of https).
I performed an upgrade of Nexus yesterday and I'm wondering if this resolved the Jersey problems. If not, do you know which repository it is in? Currently it seems like all repositories are working as expected. Tobias On 19.04.2012, at 23:22, Greg Logan <[email protected]> wrote: > We appear to be having problems with Jersey lately, and it seems like > the issue lies in their repository redirecting http downloads to https > (301 redirects). Is there a way to bypass their repo and use our repo > as the primary mirror? It seems silly to put ourselves on the mercy of > other projects when we don't have to. > > G > > _______________________________________________ > Matterhorn mailing list > [email protected] > http://lists.opencastproject.org/mailman/listinfo/matterhorn > > > To unsubscribe please email > [email protected] > _______________________________________________ _______________________________________________ Matterhorn mailing list [email protected] http://lists.opencastproject.org/mailman/listinfo/matterhorn To unsubscribe please email [email protected] _______________________________________________
