[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [m2e-dev] Authentication when importing project
|
No, you do not need to do anything special to access password protected repositories. m2e is expected to use credentials from settings.xml and either download artifacts or fail downloads, never show authentication popup.
There was a bug 440273 [1] in m2e 1.5.x, which explains unexpected auth popup, but I can't tell why m2e does not use provided credentials.
I suggest you try latest m2e 1.6 milestone build, which at least has the fix for bug 440273. If there is still a problem with authentication, I will need to understand better your network setup: protocol type, whether http proxy is involved, kind of authentication used, etc.
On Sat, May 9, 2015, at 02:37 PM, Philippe Riand wrote:
Now, these projects rely on private maven repo that is password protected. The url/user/password are defined in .m2/settings.xml within a profile that is made active.
When I create/import the projects within an environment that already have all the dependencies in its local maven repo, it works like a charm. But if it doesn’t have these dependencies local, it prompts me for a user/pwd for every single dependency it tries to download, from the same repo. On the other hand, if I create the projects, do not import them using the aforementioned api, but then import them using the import dialog, then it works (the dependencies are downloaded and it doesn’t prompt me)
Question: is there a credential manager to setup before calling the import API? It sees the active profile because it tries to reach the server, but it doesn’t use the credentials from settings.xml.
_______________________________________________
m2e-dev mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
