I've got a similar setup on 4.0.7 without any issues. I'm using a default distribution with a custom repo containing all my required features (built with karaf-maven-plugin:features-add-to-repository). I've made the same changes to comment out org.ops4j.pax.url.mvn.repositories.
On 8 December 2016 at 11:58, Jean-Baptiste Onofré <[email protected]> wrote: > Hi Jochen, > > did it work with 4.0.6 (so a regression) ? > Is the enterprise features XML present in the system folder at the first > boot ? > > If so, I consider this as a blocker (it could be related to the changes we > did on Pax URL). > > Let me try to reproduce. > > Thanks for the report ! > > Regards > JB > > > On 12/08/2016 12:11 PM, jochenw wrote: > >> Hello, >> >> in my org.ops4j.pax.url.mvn.cfg, I have commented all remote repositories, >> since I want Karaf only to search for artifacts in the default >> repositories: >> >> #org.ops4j.pax.url.mvn.repositories= \ >> # http://repo1.maven.org/maven2@id=central, \ >> ... >> >> My custom distribution contains everything I need in karaf/system, and my >> own bundles in an additional karaf/myrepo folder, which I have added to >> the >> default repositories. >> >> Since Karaf 4.0.7 (at least there I observed this the first time), >> sometimes >> Karaf tries to load the enterprise xml feature file from repo1.maven.org >> anyways, which fails, since the server has no connection to the internet. >> It >> also doesn't try to retrieve that from the local repo after the failure, >> so >> the startup hangs. When I restart Karaf after that, most of the times it >> starts correctly, so uses the local defaultRepositories to retrieve the >> artifacts from, including all feature xml files. >> >> Has anybody also seen this? Is there a way to grant that Karaf never tries >> to retrieve things from the public repos? Up to 4.0.4, I have never seen >> this behavior, and I haven't changed org.ops4j.pax.url.mvn.cfg. >> >> Regards, >> Jochen >> >> 2016-12-07 11:21:35,308 | WARN | pool-6-thread-1 | AetherBasedResolver >> | 1 - org.ops4j.pax.logging.pax-logging-api - 1.8.5 | Error resolving >> artifactorg.apache.karaf.features:enterprise:xml:features:4.0.7:Could not >> transfer artifact org.apache.karaf.features:enterprise:xml:features:4.0.7 >> from/to central (http://repo1.maven.org/maven2/): Connect to >> repo1.maven.org:80 [repo1.maven.org/151.101.36.209] failed: Connection >> timed >> out >> >> >> >> -- >> View this message in context: http://karaf.922171.n3.nabble. >> com/Avoird-default-value-for-org-ops4j-pax-url-mvn-repositor >> ies-tp4048924.html >> Sent from the Karaf - User mailing list archive at Nabble.com. >> >> > -- > Jean-Baptiste Onofré > [email protected] > http://blog.nanthrax.net > Talend - http://www.talend.com >
