I had the same problem as issue #29 when I tried to access an authenticated Nexus repository via Ivypot.
The issue seems to be that our company repository uses a different authentication realm which must be configured in the ivysettings.xml that is generated by ivypot.
You can check this if you run your gradle build with debug logging and see something like this:
In this case "MyRealm" is the realm which must be configured in ivysettings.xml.
Since the file is always regenerated by Ivypot, I prepared a fix which adds the realm property to the credentials and writes the value to the generated ivysettings.xml file. Afterwards I could resolve my dependencies without any issues my defining my repository like this:
I had the same problem as issue #29 when I tried to access an authenticated Nexus repository via Ivypot. The issue seems to be that our company repository uses a different authentication realm which must be configured in the ivysettings.xml that is generated by ivypot.
You can check this if you run your gradle build with debug logging and see something like this:
In this case "MyRealm" is the realm which must be configured in ivysettings.xml.
Since the file is always regenerated by Ivypot, I prepared a fix which adds the realm property to the credentials and writes the value to the generated ivysettings.xml file. Afterwards I could resolve my dependencies without any issues my defining my repository like this: