Hi everyone,
I'm still stuck at the "mvn deploy" stage of the release process.
I'm not sure if anyone did anything last time to re-activate my Nexus
account (Carsten?) but it seems to "come and go": yesterday i wasn't
able to login, this morning i could login and tonight again i get
"invalid user"
Is there a number of failed attempts after which the Nexus account is
frozen for a period of time? Maybe my attempts at deploying are causing
this.
After many attempts, at one point "mvn deploy" managed to upload the
first pom but when it got to the next upload again I got 401!
It's quite confusing and I don't what I'm doing wrong. I tried putting
the password in clear in my settings but to no avail.
Anyway as long as my account is frozen I can't do much.
Any suggestion is welcome.
Thanks,
-arjun
On 01/06/2012 10:12 AM, Arjun Panday wrote:
Thanks to whoever opened my Nexus account!
I can login now and org.apache.felix appears under "Staging Profiles",
but...
I still get the 401 error! :(
Uploading:
https://repository.apache.org/content/repositories/snapshots/org/apache/felix/servicediagnostics/0.1.0-SNAPSHOT/servicediagnostics-0.1.0-20120106.091027-1.pom
3/3K
[INFO]
------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO]
------------------------------------------------------------------------
[INFO] Error deploying artifact: Failed to transfer file:
https://repository.apache.org/content/repositories/snapshots/org/apache/felix/servicediagnostics/0.1.0-SNAPSHOT/servicediagnostics-0.1.0-20120106.091027-1.pom.
Return code is: 401
any idea?
-arjun
On 01/04/2012 05:48 PM, Arjun Panday wrote:
Good point Carsten,
Nexus doesn't seem to know me at all, and when I try "forgot password"
and enter my apache id and email, it says "Invalid Username".
With whom should I request access?
-arjun
On 01/04/2012 05:28 PM, Carsten Ziegeler wrote:
Hi,
I just tested today and it worked for me. Your settings look fine to
me. Maybe you need to be added to the Nexus instance in order to be
able to deploy to the staging repository?
Arjun, can you test logging into repository.apache.org (with your
apache credentials) and then look if you see the Felix project on the
left under "Staging Repositories"?
Regards
Carsten
2012/1/4 Arjun Panday<arjun.pan...@alcatel-lucent.com>:
Hi Ken,
No, I've tried again just now and keep getting the 401 error.
I don't know if others are still facing the same issue.
If it works for you let me know!
Thanks,
Arjun
On 01/04/2012 02:48 AM, Ken Gilmer wrote:
Sorry I can't provide any help in fixing this but am wondering...is it
working now? I'm planning on a httplite release shortly.
thx!
ken
On Fri, Dec 30, 2011 at 4:51 PM, Arjun Panday
<arjun.pan...@alcatel-lucent.com> wrote:
Thanks Carsten,
I guess I should not proceed with the release without this step, so I'll
just try again later.
Regards,
Arjun
On 12/30/2011 07:36 AM, Carsten Ziegeler wrote:
Hi,
I see the same error when the Apache Jenkins instance tries to deploy
snapshots of Sling, so I fear it's rather a problem with the snapshot
repository than with your settings.
Regards
Carsten
2011/12/30 Arjun Panday<arjun.pan...@alcatel-lucent.com>:
Hi everyone,
It's my turn to go through the ring of fire and attempt a release :)
"mvn release:prepare -DdryRun=true" was successful and i'm now trying
to
publish a snapshot, but I get the infamous 401 HTTP error:
[INFO] Error deploying artifact: Failed to transfer file:
https://repository.apache.org/content/repositories/snapshots/org/apache/felix/servicediagnostics/0.1.0-SNAPSHOT/servicediagnostics-0.1.0-20111229.225958-1.pom.
Return code is: 401
I know it's supposed to be something with my settings.xml but I can't
figure
out what. Below is my settings.xml with the apache servers, username
and
password (removed!). Am I missing a server entry? Can someone help me
figure
out what I did wrong?
I also checked my pom's parent:
<parent>
<groupId>org.apache.felix</groupId>
<artifactId>felix-parent</artifactId>
<version>2.1</version> <!-- should this be 3-SNAPSHOT ? -->
<relativePath>../../pom/pom.xml</relativePath>
</parent>
Thanks,
Arjun
<settings>
<servers>
<!-- To publish a snapshot of some part of Maven -->
<server>
<id>apache.snapshots.https</id>
<username>apanday</username>
<password>{encrypted password}</password>
</server>
<!-- To publish a website of some part of Maven -->
<server>
<id>apache.website</id>
<username>apanday</username>
<filePermissions>664</filePermissions>
<directoryPermissions>775</directoryPermissions>
</server>
<!-- To stage a release of some part of Maven -->
<server>
<id>apache.releases.https</id>
<username>apanday</username>
<password>{encrypted password}</password>
</server>
<!-- To stage a website of some part of Maven -->
<server>
<id>stagingSite</id> <!-- must match hard-coded repository
identifier in
site:stage-deploy -->
<username>apanday</username>
<filePermissions>664</filePermissions>
<directoryPermissions>775</directoryPermissions>
</server>
</servers>
<profiles>
<profile>
<id>release</id>
<properties>
<gpg.passphrase>{encrypted password}</gpg.passphrase>
</properties>
</profile>
</profiles>
</settings>
