Pax Runner takes 5 minutes to start - looking for scm.ops4j.org. [PAXRUNNER-437]

[ops4j-issues]

Dutch Dude created PAXRUNNER-437

I noticed that recently it takes 5 minutes to start up pax-runner. It
looks like it is going out to some website (207.223.242.218) that is
unreachable.

Please advise.

Kind Regards,

Dutch.

C:\xxxxxxxxx>mvn -o -f pom-server.xml -s settings.xml
INFO Scanning for projects...
INFO
INFO
------------------------------------------------------------------------
INFO Building XYZ 1.0.1-SNAPSHOT
INFO
------------------------------------------------------------------------
INFO
INFO — maven-pax-plugin:1.5:provision (default-cli) @ server-
runner —
WARNING Skipping non-bundle artifact commons-logging:commons-
logging:jar:1.1:compile
WARNING Skipping non-bundle artifact log4j:log4j:jar:1.2.12:compile
WARNING Skipping non-bundle artifact logkit:logkit:jar:1.0.1:compile
WARNING Skipping non-bundle artifact avalon-framework:avalon-
framework:jar:4.1.3:compile
INFO Installing xxx
__ __
__ __ _ __ _____

\/ \/ \/ \/ \/ \/

Pax Runner (1.8.5) from OPS4J - http://www.ops4j.org
----------------------------------------------------

<And it is sitting here for 5 minutes(timed)>

---

Votes: 0, Watches: 2

[ops4j-issues]

Toni Menzel commented

We'll need a new release to fix this. Alternatively you can pass your own runner.properties to circumvent the now-incorrect locations.

[ops4j-issues]

Dutch Dude commented

Can you elaborate on that a bit?
I am trying to find the documentation on how and where to pass those properties. I looked on the Configuration Options page, but nothing stands out to me.

Alternatively, can I add an entry in the hosts file for scm.ops4j.org to point to the correct, new IP address?