Hello, Without being particularly knowledgeable, I'd suggest to check these two properties first:
# Path to the local Maven settings file. #org.ops4j.pax.url.mvn.settings= and # If set to true, the following property will not allow any certificate to be used # when accessing Maven repositories through SSL # org.ops4j.pax.url.mvn.certificateCheck=true . Maybe try to point to the settings.xml explicitly or in case of an ssl connection to a remote machine check if a missing certificate is blocking the connection. I'm sure JB or someone else could give a more reliable hint here. Regards, Vassil На пн, 19.07.2021 г. в 11:29 ч. Lukasz Lech <[email protected]> написа: > Hello, > > > > I have problem getting artifacts from private company maven repository. > > > > The repository and the credentials are defined in my settings.xml, and > maven command is definitely picking them. However, it seems that karaf is > not. > > > > If I don't define the repository in org.ops4j.pax.url.mvn.cfg, I see a > stack trace that Karaf checks default repositories, but not those defined > in settings.xml. > > > > If I add our repository to the org.ops4j.pax.url.mvn.cfg : > org.ops4j.pax.url.mvn.repositories it says: Not authorized, as if Karaf was > failing to pull credentials from settings.xml correctly. > > > > Most of artifacts needed are in 2nd private repository, that requires no > auth, and it was configured for Karaf, but some artifacts are not there > (from the other part of the organization) and can be available only from > repository that requires credentials, so I have a problem if I do a clean > start (deleting local repository). > > > > How to configure karaf so that it pulls credentials correctly? Is it a > bug? I'm using 4.2.8 > > > > P.S. I'm sorry if I won't be able to give any fallback, but I'm not able > to respond to the topics using Nabble. I can do posts by sending mail to > [email protected], but I'm unable to respond, since I get no email > from the group to my email account. I've already asked about that issue, > but without efford. So most likely I'm able only to post new issues. > > > > Best regards, > > Lukasz Lech >
