Yeah I can confirm, that I too couldn't find any reference to invalid login attempts in my Artifactory logs.
Chris ________________________________________ Von: Mehul Sanghvi <mehul.sang...@gmail.com> Gesendet: Dienstag, 9. Februar 2016 21:49 An: Maven Users List Betreff: Re: debugging maven-deploy-plugin:deploy-file What should I be looking at on the server side ? I have access to it, with admin privs. I don't know much about it, and am the admin because the people that set it up have all left the company. I'm "it" by default :) I looked at nexus.log, but nothing happens when I actually run maven with the pom.xml. I have compared the help:effective-settings output for the jars-upload vs zip-upload profile, and the only difference was the profile name. I am trying to figure out from the server side if there is anything configured incorrectly somewhere, or some role/privilege that is incorrect, though that doesn't make sense, as its the same user writing tot he same repository in both cases. On Tue, Feb 9, 2016 at 10:40 AM, Christofer Dutz <christofer.d...@c-ware.de> wrote: > In my case I'm the only user and admin of the Repo Manager. > > And I know that I didn't update anything or even log-in to the front end > for months now. Also I didn't change anything with my settings.xml (even if > I thought I had but it turned out that it was in another settings.xml). > It's still the same as in one really old backup. > > I'll hope to find some time to investigate this as I know it will bite me > pretty soon. > > Chris > > ________________________________________ > Von: anders.g.ham...@gmail.com <anders.g.ham...@gmail.com> im Auftrag von > Anders Hammar <and...@hammar.net> > Gesendet: Dienstag, 9. Februar 2016 16:27 > An: Maven Users List > Betreff: Re: debugging maven-deploy-plugin:deploy-file > > Please keep in mind that there could be authorization rules in the > repository manager that gives access to some groupIds but not others, for > example. You should contact the ones responsible for your repo manager > instance and have them help you! > > /Anders > > On Tue, Feb 9, 2016 at 4:16 PM, Christofer Dutz <christofer.d...@c-ware.de > > > wrote: > > > Just to add my 50ct ... I too encountered a similar problem a few days > ago > > and am still having it. > > > > While I had a settings.xml that worked fine for ages I got the exact same > > Unauthorized errors. > > At first I thought I had a problem in my settings but I couldn't find > one. > > I "resolved" the problem, by disabling the settings.xml and pulling from > > maven central instead of my private repo ... but that's not a real > > resolution. > > > > I was also using a pretty recent 3.3.x version (not the 3.3.9 cause it > > breaks most of my important plugins) > > My repo is an Artifactory (Haven't updated that for quite some time) > > > > As I don't seem to be alone with this eventually I'll use Wireshark > > investigate what's going over the wire. Mabe this will help find out > what's > > going wrong. > > > > Chris > > > > ________________________________________ > > Von: Mehul Sanghvi <mehul.sang...@gmail.com> > > Gesendet: Dienstag, 9. Februar 2016 15:02 > > An: Maven Users List > > Cc: i...@soebes.de > > Betreff: Re: debugging maven-deploy-plugin:deploy-file > > > > The repositoryId is the same for both. They are getting uploaded to the > > same repository. > > > > So face I have tested the following: > > > > 1. verified username/password by logging into the web ui > > > > 2. verified that server id in settings.xml matches the distribution > > repository id in the pom.xml > > > > 3. verified correct settings.xml was being used. I used > > > > mvn help:effective-settings > > > > 4. verified the url is correct and the protocol being used is http and > not > > https > > > > 5. using one of the latest versions of maven i.e. 3.3.3 > > > > > > > > > > > > On Tue, Feb 9, 2016 at 4:03 AM, Adrien Rivard <adrien.riv...@gmail.com> > > wrote: > > > > > Hi, > > > > > > > > > I'm guessing you have a mismatch between the repositories ids you have > at > > > execution and the configured <server><id> in your settings.xml (where > the > > > username/password are). > > > Probably the repository id for upload-zip stuff is different that the > one > > > for upload-jars? > > > > > > > > > > > > On Tue, Feb 9, 2016 at 1:54 AM, Mehul Sanghvi <mehul.sang...@gmail.com > > > > > wrote: > > > > > > > > > > > > > > > I have attached a copy of the pom.xml that I am using. > > > > > > > > > > > > > > > > On Mon, Feb 8, 2016 at 4:05 AM, Karl Heinz Marbaise < > khmarba...@gmx.de > > > > > > > wrote: > > > > > > > >> Hi, > > > >> > > > >> On 2/8/16 6:43 AM, Mehul Sanghvi wrote: > > > >> > > > >>> I have a project with multiple modules and sub-modules. Two of > the > > > >>> modules, use > > > >>> the same maven-deploy-plugin:deploy-file logic, just the artefacts > > they > > > >>> are > > > >>> working > > > >>> > > > >> > > > >> > > > >> Can you show an example of your deploy-file logic? Cause if you are > > > >> really using deploy-file goal within your pom file and in your life > > > cycle > > > >> there is something wrong... > > > >> > > > >> Kind regards > > > >> Karl Heinz Marbaise > > > >> > > > >> with are different. One module uploads designated JARs to Nexus. > The > > > >>> other is > > > >>> meant for uploading ZIP files. Both are activated only if their > > > >>> respective > > > >>> profiles > > > >>> are activated, -Pupload-jars and -Pupload-zips respectively. Both > > > >>> modules > > > >>> share the same settings.xml information regarding repositories and > > > >>> servers. > > > >>> > > > >>> > > > >>> Upload-jars is able to successfully upload the JARs using > > deploy-file. > > > >>> Upload-zips always fails with: > > > >>> > > > >>> Return code is: 401, ReasonPhrase:Unauthorized > > > >>> > > > >>> How do I figure out the credentials that are being used ? When I > use > > > >>> > > > >>> mvn -X > > > >>> > > > >>> I do not see anything that would indicate what user/passwd > > combination > > > is > > > >>> being used. Any thoughts or suggestions ? > > > >>> > > > >> > > > >> > --------------------------------------------------------------------- > > > >> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > > > >> For additional commands, e-mail: users-h...@maven.apache.org > > > >> > > > >> > > > > > > > > > > > > -- > > > > Mehul N. Sanghvi > > > > email: mehul.sang...@gmail.com > > > > > > > > > > > > --------------------------------------------------------------------- > > > > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > > > > For additional commands, e-mail: users-h...@maven.apache.org > > > > > > > > > > > > > > > > -- > > > Adrien Rivard > > > > > > > > > > > -- > > Mehul N. Sanghvi > > email: mehul.sang...@gmail.com > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > > For additional commands, e-mail: users-h...@maven.apache.org > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > > -- Mehul N. Sanghvi email: mehul.sang...@gmail.com --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
