debugging maven-deploy-plugin:deploy-file
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 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 ? cheers, mehul -- Mehul N. Sanghvi email: mehul.sang...@gmail.com
Re: debugging maven-deploy-plugin:deploy-file
Hi, If it is effectively using the same configuration, the problem could be on the nexus level (users / permission). Try uploading it directly from the nexus GUI. That said I don't recall anything that would prevent iploading zip and not jars so your problem can still be on maven level. Can you try without profiles for example ? (avoid profile if it possible). Also Nexus logs can have useful informations if you have access to them. On Mon, Feb 8, 2016 at 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 > 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 ? > > > cheers, > > mehul > > -- > Mehul N. Sanghvi > email: mehul.sang...@gmail.com > -- Adrien Rivard
Re: debugging maven-deploy-plugin:deploy-file
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
Re: debugging maven-deploy-plugin:deploy-file
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
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
http://maven.apache.org/POM/4.0.0"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd";>
4.0.0
GROUP.ID
publish-zip-artifacts
ZIP PUBLISH
pom
ORG.GROUP.ID
SOME-ARTIFACT-ID
1.2.3-SNAPSHOT
${project.distributionManagement.snapshotRepository.id}
${project.distributionManagement.snapshotRepository.url}
GROUP.ID
PROFILE-ZIP-UPLOAD
integration-releases
Internal Release Repository
http://nexus.internal.com:8081/nexus/content/repositories/repo-releases
true
integration-snapshot
Internal Snapshot Repository
http://internal.nexus.com:8081/nexus/content/repositories/repo-snapshot
false
org.apache.maven.plugins
maven-deploy-plugin
2.7
deploy-artifact-zip
install
deploy-file
${repositoryId}
${url}
${groupId}
SOME-ARTIFACT
${project.version}
${project.parent.basedir}/path/to/target-${osArch}-${osName}.zip
${release.platform}
true
zip
ORG.GROUP.ID
SOME-ASSEMBLY
${project.version}
pom
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: debugging maven-deploy-plugin:deploy-file
Hi, I'm guessing you have a mismatch between the repositories ids you have at execution and the configured 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 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 > 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
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 wrote: > Hi, > > > I'm guessing you have a mismatch between the repositories ids you have at > execution and the configured 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 > 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 > > 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
AW: debugging maven-deploy-plugin:deploy-file
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 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 wrote: > Hi, > > > I'm guessing you have a mismatch between the repositories ids you have at > execution and the configured 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 > 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 > > 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
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 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 > 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 > wrote: > > > Hi, > > > > > > I'm guessing you have a mismatch between the repositories ids you have at > > execution and the configured 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 > > 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 > > > > 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 > >
AW: debugging maven-deploy-plugin:deploy-file
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 im Auftrag von Anders Hammar 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 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 > 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 > wrote: > > > Hi, > > > > > > I'm guessing you have a mismatch between the repositories ids you have at > > execution and the configured 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 > > 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 > > > > 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 th
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 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 im Auftrag von > Anders Hammar > 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 > > 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 > > 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 > > wrote: > > > > > Hi, > > > > > > > > > I'm guessing you have a mismatch between the repositories ids you have > at > > > execution and the configured 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 > > > > 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
AW: debugging maven-deploy-plugin:deploy-file
Yeah I can confirm, that I too couldn't find any reference to invalid login attempts in my Artifactory logs. Chris Von: Mehul Sanghvi 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 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 im Auftrag von > Anders Hammar > 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 > > 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 > > 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 > > wrote: > > > > > Hi, > > > > > > > > > I'm guessing you have a mismatch between the repositories ids you have > at > > > execution and the configured 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 > > > > wrote: > > > > > > > > > > > > > > > I have attached a copy of the pom.xml that I a
Re: debugging maven-deploy-plugin:deploy-file
I was able to manually upload using the following command-line: mvn deploy:deploy-file -B -V -s /path/to/build/dir/maven/settings-unix-buildmachine.xml -DrepositoryId=SNAPSHOTS-REPO-ID -Durl= http://internal.nexus.host.com/nexus/content/repositories/snapshots-repo-being-used -DgeneratePom=true -DgroupId=COM.GROUP.ID -Dversion=1.2.3.4.5-SNAPSHOT -DartifactId=ARTIFACT-ID -Dfile=ZIP-FILE.zip -Dpackaging=zip -Dclassifier=linux Using mvn-3.0.5 it took just under 19 minutes to upload the zip file. Using mvn-3.3.3 it took 22 seconds. So there must be something wrong with the POM file that we are using. I will try and narrow it down and see what I can find. On Tue, Feb 9, 2016 at 5:44 PM, Christofer Dutz wrote: > Yeah I can confirm, that I too couldn't find any reference to invalid > login attempts in my Artifactory logs. > > Chris > > > Von: Mehul Sanghvi > 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 im Auftrag > von > > Anders Hammar > > 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 > > > 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: > > >
Re: debugging maven-deploy-plugin:deploy-file
I was able to resolve it, after doing a more thorough comparison of the help:effective-settings output. I had to clean out all the noise in the output first. After that I used Emacs and Ediff to do the diff between the two log outputs I had. That's when the following was noticed: Working POM:distributionManagement/repository/id = blah-blah-snapshotS Failing POM: distributionManagement/repository/id = blah-blah-snapshot It helped to look at it in different colours with Emacs/ediff. On a slightly different note, is there a way to get help:effective-settings to only output the effective pom to a log file, rather than using shell re-direct or tee which will capture all the noise as well ? cheers, mehul On Wed, Feb 10, 2016 at 12:11 PM, Mehul Sanghvi wrote: > I was able to manually upload using the following command-line: > > mvn deploy:deploy-file -B -V -s > /path/to/build/dir/maven/settings-unix-buildmachine.xml > -DrepositoryId=SNAPSHOTS-REPO-ID -Durl= > http://internal.nexus.host.com/nexus/content/repositories/snapshots-repo-being-used > -DgeneratePom=true -DgroupId=COM.GROUP.ID -Dversion=1.2.3.4.5-SNAPSHOT > -DartifactId=ARTIFACT-ID -Dfile=ZIP-FILE.zip -Dpackaging=zip > -Dclassifier=linux > > > Using mvn-3.0.5 it took just under 19 minutes to upload the zip file. > Using mvn-3.3.3 it took 22 seconds. > > > So there must be something wrong with the POM file that we are using. I > will try and narrow it down and see what I can find. > > > > On Tue, Feb 9, 2016 at 5:44 PM, Christofer Dutz > wrote: > >> Yeah I can confirm, that I too couldn't find any reference to invalid >> login attempts in my Artifactory logs. >> >> Chris >> >> ____ >> Von: Mehul Sanghvi >> 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 im Auftrag >> von >> > Anders Hammar >> > 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. >&
