[
https://issues.apache.org/jira/browse/KARAF-2828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13970076#comment-13970076
]
Martin Lichtin commented on KARAF-2828:
---------------------------------------
Will it be possible to back-port this change for an upcoming 3.x.y release?
It's quite a showstopper when trying to move up from 2.3.x.
> Reintroduce system as a default repository
> ------------------------------------------
>
> Key: KARAF-2828
> URL: https://issues.apache.org/jira/browse/KARAF-2828
> Project: Karaf
> Issue Type: Bug
> Components: karaf-core
> Affects Versions: 3.0.0
> Reporter: Jean-Baptiste Onofré
> Assignee: Guillaume Nodet
> Fix For: 4.0.0
>
>
> Now, Karaf firstly uses the remote repositories to resolve artifacts, and
> "fall" back on "local" repository after.
> It means that depending of the connection on the machine, the Karaf bootstrap
> can be very long.
> Karaf should first use both $HOME/.m2/repository and system repository as
> default one, and go on remote repositories only if the artifacts are not
> resolved on the default one.
> Anyway, this required a change in pax-url-aether (to support default
> repository).
--
This message was sent by Atlassian JIRA
(v6.2#6252)
