Jason,
can you point me to the template you are referring to? I have no idea
where I have to look for that.
Michael
Am 2014-11-27 um 23:37 schrieb Jason van Zyl:
I think the number of ITs that need a connection to Maven Central is
very few. You need to explicitly use the template which gives
On 28 November 2014 at 08:16, Anders Hammar wrote:
> 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 used my laptop tethered to my phone.
The
I think the number of ITs that need a connection to Maven Central is very few.
You need to explicitly use the template which gives you a settings with an
external connection. By default it's isolated. Now the bootstrapping to grab
stuff you need requires an external connection. I've worked aroun
Am 2014-11-27 um 22:46 schrieb Anders Hammar:
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).
Absolutely not an option here :-(
--
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 e
Addition: if you want to reproduce this on a not locked down network.
Have a Nexus instance on your machine (localhost), run the testing once
to have all necessary dependencies. Disconnect your LAN/WLAN connection
and retry. It should fail with connection timeout.
-
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/config
