[
https://issues.apache.org/jira/browse/KARAF-4719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15565822#comment-15565822
]
Grzegorz Grzybek commented on KARAF-4719:
-----------------------------------------
Increasing start-level for pax-url-aether is good workaround, but it still
isn't 100% reliable (estimated increas from 50% reliable to 95% reliable).
Without actual change to pax-url-aether, to make it wait for ConfigurationAdmin
there's no 100% way of making this work. But pax-url-aether *can* run without
Configuration Admin...
[~gnt], [~jbonofre] what do you think about increasing start-level for
pax-url-aether?
> Aether cannot to resolve m2 repositories after adjustments in
> org.ops4j.pax.url.mvn.cfg
> ---------------------------------------------------------------------------------------
>
> Key: KARAF-4719
> URL: https://issues.apache.org/jira/browse/KARAF-4719
> Project: Karaf
> Issue Type: Bug
> Affects Versions: 4.0.5, 4.0.6
> Reporter: Antonio Maria
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> 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:
> {code}
> org.ops4j.pax.url.mvn.localRepository=${karaf.home}/${karaf.default.repository}
> {code}
> 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.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
