I would try test your expected user name and password using curl, without using Maven.
curl -u user:password http://localhost:8080/nexus/content/groups/public/org/springframework/spring-aspects/3.2.7.RELEASE/spring-aspects-3.2.7.RELEASE.pom
If it works, then focus on Maven, the Maven wagon versions in use locally and on CI, and the settings.xml and profiles being used. Use mvn -X to see what the wagon is doing on CI. If you want to be absolutely sure, possibly enable detailed Maven wagon logging.
If the authorization fails with curl, then the research can start with Nexus. Change the root logging to DEBUG in Nexus and send your request again. Examine the nexus.log file, looking for your requested path and the denial.
There is no direct downgrade option. You can use the same Nexus version you were using previously, with a backed up sonatype-work/nexus/conf configuration from that old version if the upgrade is the cause of the problem.
More advanced nexus logging tips are in this article.
On Wed, Jan 29, 2014 at 4:41 PM, jaybytez <[hidden email]> wrote:
I ran into some issues with a build, after I had done an upgrade from about
|Free forum by Nabble||Edit this page|