[KARAF-4719] Aether cannot to resolve m2 repositories after adjustments in org.ops4j.pax.url.mvn.cfg

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 4.0.5, 4.0.6
• Fix Version/s: 4.1.0
• Assignee: Grzegorz Grzybek
• Reporter: Antonio Maria
• Created: 20/Sep/16 06:23
• Updated: 19/Dec/19 17:36
• Resolved: 19/Dec/16 09:38

Description

Start levels for pax-url-aether(5) and org.apache.felix.configadmin(10) are defined in framework xml feature. Therefore pax url aether is configured after org.ops4j.pax.url.mvn.local properties are loaded.

This causes that in case of assemble Karaf using offline repository, by adjusting:

org.ops4j.pax.url.mvn.localRepository=${karaf.home}/${karaf.default.repository}

Don't really work, because is too late for aether, that is already started.

Eventually causes an error when karaf starts. The error is quite random, and happens quite often when karaf starts using the wrapper as a windows services.

By decreasing the aether starts level to any value after felix configadmin, it improves the bootstrap robustness when creating offline distribution.

Issue Links

• duplicates: KARAF-4100 [karaf-3.0.x] Error resolving artifact of feature due to org.ops4j.pax.url.mvn.cfg not loaded yet
• Is contained by: KARAF-4762 Upgrade to PaxUrl 2.5.1