As said in another e-mail, I don't think the problem is about the
download by itself. It's more the caching of the artifact in the Karaf
folder.
I would dig on a antivirus scanner or any other process that lock the
folders.
Regards
JB
On 02/02/2018 22:15, anynamus wrote:
Hi François,
This configuration was not set because we use an internal instance of
Artifactory.
I configured my settings.xml to bypass Artifactory and configured the mirror
you specified and I got almost the same error:
2018-02-02T16:08:47,582 | WARN | pool-26-thread-4 | AetherBasedResolver
| 4 - org.ops4j.pax.url.mvn - 2.5.3 | Error resolving artifact
org.apache.felix:org.apache.felix.scr:jar:2.0.12: [Could not transfer
artifact org.apache.felix:org.apache.felix.scr:jar:2.0.12 from/to US
(http://repo.maven.apache.org/maven2):
C:\Users\anynamus\.m2\repository\org\apache\felix\org.apache.felix.scr\2.0.12\org.apache.felix.scr-2.0.12.jar.part.lock
(The system cannot find the path specified)]
java.io.IOException: Error resolving artifact
org.apache.felix:org.apache.felix.scr:jar:2.0.12: [Could not transfer
artifact org.apache.felix:org.apache.felix.scr:jar:2.0.12 from/to US
(http://repo.maven.apache.org/maven2):
C:\Users\anynamus\.m2\repository\org\apache\felix\org.apache.felix.scr\2.0.12\org.apache.felix.scr-2.0.12.jar.part.lock
(The system cannot find the path specified)]
Regards.
Pascal-Eric
--
Sent from: http://karaf.922171.n3.nabble.com/Karaf-User-f930749.html
