karaf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Antonio Maria (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (KARAF-4719) Aether cannot to resolve m2 repositories after adjustments in org.ops4j.pax.url.mvn.cfg
Date Tue, 11 Oct 2016 13:10:20 GMT

    [ https://issues.apache.org/jira/browse/KARAF-4719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15565369#comment-15565369
] 

Antonio Maria commented on KARAF-4719:
--------------------------------------

My workaround doesn't require any "duplications" just modifying:

etc/startup.properties line8
from:
mvn\:org.ops4j.pax.url/pax-url-aether/2.4.7 = 5
to 
mvn\:org.ops4j.pax.url/pax-url-aether/2.4.7 = 14

I just would like not to apply that "workaround" during my build process. In other words:
To take the change into use in karaf code base.

Does it help if I made a push request?


> 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)

Mime
View raw message