[forge-issues] [JBoss JIRA] (FORGE-1321) Failure to install addons when using secure repositories

[ https://issues.jboss.org/browse/FORGE-1321?page=com.atlassian.jira.plugin... ] Vineet Reynolds edited comment on FORGE-1321 at 11/27/13 1:56 AM: ------------------------------------------------------------------ [~gastaldi], I was able to reproduce this against my local Nexus instance. I got this stacktrace dumped on the error: {noformat} Downloading: http://localhost:8081/nexus/content/groups/public/org/jboss/forge/addon/p... java.lang.RuntimeException: org.eclipse.aether.resolution.DependencyResolutionException: The following artifacts could not be resolved: org.jboss.forge.addon:configuration:jar:forge-addon:2.0.0-SNAPSHOT, org.jboss.forge.addon:configuration-api:jar:2.0.0-SNAPSHOT, org.jboss.forge.addon:configuration-impl:jar:2.0.0-SNAPSHOT, org.jboss.forge.addon:resources:jar:forge-addon:2.0.0-SNAPSHOT, org.jboss.forge.addon:projects:jar:forge-addon:2.0.0-SNAPSHOT: Could not transfer artifact org.jboss.forge.addon:configuration:jar:forge-addon:2.0.0-20131120.220705-132 from/to nexus-local-repo (http://localhost:8081/nexus/content/groups/public/): Access denied to: http://localhost:8081/nexus/content/groups/public/org/jboss/forge/addon/c... at org.jboss.forge.furnace.manager.maven.addon.MavenAddonDependencyResolver.resolveResources(MavenAddonDependencyResolver.java:105) at org.jboss.forge.furnace.manager.maven.addon.LazyAddonInfo.resolveResources(LazyAddonInfo.java:88) at org.jboss.forge.furnace.manager.maven.addon.LazyAddonInfo.getResources(LazyAddonInfo.java:39) at org.jboss.forge.furnace.manager.impl.request.DeployRequestImpl.deploy(DeployRequestImpl.java:59) at org.jboss.forge.furnace.manager.impl.request.DeployRequestImpl$1.call(DeployRequestImpl.java:49) at org.jboss.forge.furnace.impl.LockManagerImpl.performLocked(LockManagerImpl.java:48) at org.jboss.forge.furnace.manager.impl.request.DeployRequestImpl.execute(DeployRequestImpl.java:44) at org.jboss.forge.furnace.manager.impl.request.AbstractAddonActionRequest.perform(AbstractAddonActionRequest.java:57) at org.jboss.forge.furnace.manager.impl.request.InstallRequestImpl.perform(InstallRequestImpl.java:39) at org.jboss.forge.bootstrap.Bootstrap.install(Bootstrap.java:229) at org.jboss.forge.bootstrap.Bootstrap.<init>(Bootstrap.java:147) at org.jboss.forge.bootstrap.Bootstrap.main(Bootstrap.java:91) {noformat} But I'd like to state that this is most likely an issue with older Maven metadata present in the .m2/repository directory. Or it has something to do with incorrect server settings that ought to be removed from settings.xml (unnecessary entries do not cause any issue from what I've seen). Going by the Lightweight HTTP wagon internals, unnecessary entries do not cause any issue. With the lightweight HTTP wagon, the passwords are used only when a challenge is issued. The URLConnection and Authenticator classes in the JRE work together to request the password retrieved from the settings.xml (which is done only when the server requires authentication and not otherwise). We could treat this issue as resolved. was (Author: vineet.reynolds): [~gastaldi], I was able to reproduce this against my local Nexus instance. I got this stacktrace dumped on the error: {noformat} Downloading: http://localhost:8081/nexus/content/groups/public/org/jboss/forge/addon/p... java.lang.RuntimeException: org.eclipse.aether.resolution.DependencyResolutionException: The following artifacts could not be resolved: org.jboss.forge.addon:configuration:jar:forge-addon:2.0.0-SNAPSHOT, org.jboss.forge.addon:configuration-api:jar:2.0.0-SNAPSHOT, org.jboss.forge.addon:configuration-impl:jar:2.0.0-SNAPSHOT, org.jboss.forge.addon:resources:jar:forge-addon:2.0.0-SNAPSHOT, org.jboss.forge.addon:projects:jar:forge-addon:2.0.0-SNAPSHOT: Could not transfer artifact org.jboss.forge.addon:configuration:jar:forge-addon:2.0.0-20131120.220705-132 from/to nexus-local-repo (http://localhost:8081/nexus/content/groups/public/): Access denied to: http://localhost:8081/nexus/content/groups/public/org/jboss/forge/addon/c... at org.jboss.forge.furnace.manager.maven.addon.MavenAddonDependencyResolver.resolveResources(MavenAddonDependencyResolver.java:105) at org.jboss.forge.furnace.manager.maven.addon.LazyAddonInfo.resolveResources(LazyAddonInfo.java:88) at org.jboss.forge.furnace.manager.maven.addon.LazyAddonInfo.getResources(LazyAddonInfo.java:39) at org.jboss.forge.furnace.manager.impl.request.DeployRequestImpl.deploy(DeployRequestImpl.java:59) at org.jboss.forge.furnace.manager.impl.request.DeployRequestImpl$1.call(DeployRequestImpl.java:49) at org.jboss.forge.furnace.impl.LockManagerImpl.performLocked(LockManagerImpl.java:48) at org.jboss.forge.furnace.manager.impl.request.DeployRequestImpl.execute(DeployRequestImpl.java:44) at org.jboss.forge.furnace.manager.impl.request.AbstractAddonActionRequest.perform(AbstractAddonActionRequest.java:57) at org.jboss.forge.furnace.manager.impl.request.InstallRequestImpl.perform(InstallRequestImpl.java:39) at org.jboss.forge.bootstrap.Bootstrap.install(Bootstrap.java:229) at org.jboss.forge.bootstrap.Bootstrap.<init>(Bootstrap.java:147) at org.jboss.forge.bootstrap.Bootstrap.main(Bootstrap.java:91) {noformat} Going by this, and the Lightweight HTTP wagon internals, I'd concur that unnecessary or incorrect server settings should be removed from settings.xml. With the lightweight HTTP wagon, the passwords are used only when a challenge is issued. For some reason, the URLConnection and Authenticator classes in the JRE work together to request the password retrieved from the settings.xml (which is done only when the server requires authentication; obviously the server requested authentication even though anonymous access was sufficient). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira