[
https://issues.apache.org/jira/browse/KARAF-2828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13940421#comment-13940421
]
Guillaume Nodet commented on KARAF-2828:
----------------------------------------
I'm not sure we can fix it in 3.0.1 because it will require an upgrade to
pax-url 2.0
If we want to fix it in 3.0.1, we'd need a minor release of pax-url with the
fix.
> 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: Jean-Baptiste Onofré
> Fix For: 3.0.1, 3.1.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)
