[forge-issues] [JBoss JIRA] (FORGE-426) Maven ArtifactResolver/RemoteRepository not using proxy information

[Simon Gunzenreiner (Created) (JIRA)]

Maven ArtifactResolver/RemoteRepository not using proxy information
-------------------------------------------------------------------

                 Key: FORGE-426
                 URL: https://issues.jboss.org/browse/FORGE-426
             Project: Forge
          Issue Type: Enhancement
          Components: Shell
    Affects Versions: 1.0.0.Beta5
         Environment: Windows
            Reporter: Simon Gunzenreiner


When starting the Forge shell in my environment (it turns out that using a HTTP proxy is relavant), it takes a long time for the prompt to appear. When setting up the plugins component, multiple error indications appear after a few minutes. All of this basically results in Forge not even being usable for the first steps described in the documentation - and might be related to https://issues.jboss.org/browse/FORGE-421.

To confirm my suspicion that this could be related to using a HTTP proxy, I ran Forge with remote debugging. What I found is this:

The MavenDependencyFacet, using the DefaultModelBuilder, initializes RemoteRepository objects without Proxy information.These RemoteRepositories are eventually used in WagonRepositoryConnector to connect to get artifacts (again - without applying a Proxy information). MAVEN_HOME btw. points to a valid Maven installation (with appropriate repository mirrors configured), and in the user home directory a valid settings.xml has even configured HTTP proxy information - but both do not seem to matter.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira