Continuum

error when trying to run data management tool when behind a proxied firewall

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 1.1-beta-3
  • Fix Version/s: 1.1
  • Component/s: Data Management
  • Labels:
    None
  • Complexity:
    Intermediate
  • Number of attachments :
    0

Description

Using -Dhttp.proxyHost=proxyhost.com, -Dhttp.proxyPort=80 -Dproxy.User=myuserid -Dhttp.proxyPassword=mypassword doesn't work
Setting -Djava.net.useSystemProxies=true doesn't work
Setting -Dhttp.auth.ntlm.domain=mydomain doesn't work
Nor does it pick up the proxy settings in my settings.xml file.

0 [main] INFO org.apache.maven.continuum.management.DataManagementCli - Processing Continuum database...
Exception in thread "main" org.apache.maven.artifact.resolver.MultipleArtifactsNotFoundException: Missing:
----------
1) org.apache.maven.continuum:data-management-jdo:jar:1.1-beta-3

Try downloading the file manually from the project website.

Then, install it using the command:
mvn install:install-file -DgroupId=org.apache.maven.continuum -DartifactId=data-management-jdo \
-Dversion=1.1-beta-3 -Dpackaging=jar -Dfile=/path/to/file

Path to dependency:
1) dummy:dummy:pom:1.0
2) org.apache.maven.continuum:data-management-jdo:jar:1.1-beta-3

----------
1 required artifact is missing.

for artifact:
dummy:dummy:pom:1.0

from the specified remote repositories:
central (http://repo1.maven.org/maven2)

at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:305)
at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:272)
at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:243)
at org.apache.maven.continuum.management.DataManagementCli.downloadArtifact(DataManagementCli.java:292)
at org.apache.maven.continuum.management.DataManagementCli.processDatabase(DataManagementCli.java:173)
at org.apache.maven.continuum.management.DataManagementCli.main(DataManagementCli.java:146)

Issue Links

Activity

Hide
Tomislav Stojcevich added a comment -

A workaround was to download data-management-cli.1.1-beta-3-app.pom manually from the repo, save it as pom.xml, than run mvn dependency:resolve. That downloads all required dependencies into my local repo and does use the proxy settings in settings.xml.

Show
Tomislav Stojcevich added a comment - A workaround was to download data-management-cli.1.1-beta-3-app.pom manually from the repo, save it as pom.xml, than run mvn dependency:resolve. That downloads all required dependencies into my local repo and does use the proxy settings in settings.xml.
Hide
Olivier Lamy added a comment -

I need more information on your proxy : what kind of proxy are you using ?
Because I have done this on a solaris machine using a windows proxy with auth (only -Dhttp.proxyHost=proxyhost.com, -Dhttp.proxyPort=80) and was working fine.

Show
Olivier Lamy added a comment - I need more information on your proxy : what kind of proxy are you using ? Because I have done this on a solaris machine using a windows proxy with auth (only -Dhttp.proxyHost=proxyhost.com, -Dhttp.proxyPort=80) and was working fine.
Hide
Tomislav Stojcevich added a comment -

not sure what kind of proxy i am using, i do know that i have to specify proxyHost, proxyPort, username and password. This username and password is different from my windows username and password.

Show
Tomislav Stojcevich added a comment - not sure what kind of proxy i am using, i do know that i have to specify proxyHost, proxyPort, username and password. This username and password is different from my windows username and password.
Hide
Damien Lecan added a comment -

Should DMC read settings.xml ?

Show
Damien Lecan added a comment - Should DMC read settings.xml ?
Hide
Emmanuel Venisse added a comment -

post beta-3, it read the settings.xml

Show
Emmanuel Venisse added a comment - post beta-3, it read the settings.xml
Hide
Francis De Brabandere added a comment -

Olivier, i got the same problems while having this ~/.m2/settings.xml
using the -Dhttp.proxyHost=proxyhost.com, -Dhttp.proxyPort=8080 everything works fine

(exporting from beta3)

<settings>
<proxies>
<proxy>
<active>true</active>
<protocol>http</protocol>
<host>http-proxy.xxx.com</host>
<port>8080</port>
<nonProxyHosts>www.google.com|*.xxx.local</nonProxyHosts>
</proxy>
</proxies>
</settings>

Show
Francis De Brabandere added a comment - Olivier, i got the same problems while having this ~/.m2/settings.xml using the -Dhttp.proxyHost=proxyhost.com, -Dhttp.proxyPort=8080 everything works fine (exporting from beta3) <settings> <proxies> <proxy> <active>true</active> <protocol>http</protocol> <host>http-proxy.xxx.com</host> <port>8080</port> <nonProxyHosts>www.google.com|*.xxx.local</nonProxyHosts> </proxy> </proxies> </settings>
Hide
Emmanuel Venisse added a comment -

Fixed.

Show
Emmanuel Venisse added a comment - Fixed.

People

Vote (3)
Watch (2)

Dates

  • Created:
    Updated:
    Resolved: