I've been in the same position as you. My solution back then was to work on Maven (and also some plugins) on my private MBP connecting to Internet through other channels (an open guest network). I don't know if the mrm-maven-plugin could solve some of this. It does for plugin ITs, but is not used everywhere.
/Anders On Thu, Nov 27, 2014 at 10:29 PM, Michael Osipov <[email protected]> wrote: > Hi folks, > > recently I began fixing issues at work and let tests run on powerful > machines in the background. Unfortunately, I cannot really make any > progress here. More than 80 % of all unit/integration tests fail because > they are not self-contained. They all have Maven Central > hardcoded/configured somewhere and that results in a "connection timeout". > > I am in a highly isolated environment where outbound traffic works only > through a HTTP proxy, therefore I have installed a Nexus instance years ago > and route all requests through that. Because of the 'awkward' test design > that mirror (from my settings.xml) is completely ignored. > > For me, there are two consequences: > > 1. I have to stall or reduce my bug fixing activities at work, losing a > lot of productivity which I cannot have at home. Various operating systems > and multicore Xeon CPUs. > 2. While performing the recent bug cleanup, some people responded to the > closures. I kindly asked them either to provide or retest patches against > latest versions with successful unit/integration tests. If those people are > in the same situation like I am, we lose contributors in complete > frustration which I fully understand. > > Is anyone of you in the same locked down situation and have any remedy to > this or know how we can solve this? > > Michael > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
