[jira] (MNG-5443) Maven 3.0.5 regression in release:perform: "Host name may not be null"

["Jesse Glick (JIRA)" <ji...@codehaus.org>]

    [ https://jira.codehaus.org/browse/MNG-5443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=320683#comment-320683 ] 

Jesse Glick commented on MNG-5443:
----------------------------------

With {{-e}}:

{code:none}
java.lang.IllegalArgumentException: Host name may not be null
	at org.apache.maven.wagon.providers.http.httpclient.HttpHost.<init>(HttpHost.java:79)
	at org.apache.maven.wagon.providers.http.httpclient.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:501)
	at org.apache.maven.wagon.providers.http.httpclient.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:906)
	at org.apache.maven.wagon.providers.http.httpclient.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:805)
	at org.apache.maven.wagon.shared.http4.AbstractHttpClientWagon.execute(AbstractHttpClientWagon.java:746)
	?
{code}

Debugging made considerably more complicated by lack of deployed {{*-sources.jar}} for shaded artifacts, but everything looks fine at line 746 at least. Using {{-X}} turned up nothing more of interest.

Setting {{-Dmaven.wagon.http.ssl.insecure=true}} (either on {{mvn}} command line, or in {{$MAVEN_OPTS}}) as per WAGON-385 did not help. I also tried {{.allowall}} and {{.ignore.validity.dates}} without luck.
                
> Maven 3.0.5 regression in release:perform: "Host name may not be null"
> ----------------------------------------------------------------------
>
>                 Key: MNG-5443
>                 URL: https://jira.codehaus.org/browse/MNG-5443
>             Project: Maven 2 & 3
>          Issue Type: Bug
>          Components: Deployment
>         Environment: Ubuntu 12.04 32-bit, JDK 7u15
>            Reporter: Jesse Glick
>            Priority: Blocker
>         Attachments: ssl.png
>
>
> With Maven 3.0.4 deploying to our Artifactory server from {{release:perform}} works fine:
> {code:none}
> [INFO] --- maven-deploy-plugin:2.7:deploy (default-deploy) @ ... ---
> Uploading: https://....artifactoryonline.com/.../releases/.../8/...-8.pom
> Uploaded: https://....artifactoryonline.com/.../releases/.../8/...-8.pom (16 KB at 11.1 KB/sec)
> {code}
> But the same command in Maven 3.0.5 fails:
> {code:none}
> [INFO] --- maven-deploy-plugin:2.7:deploy (default-deploy) @ ... ---
> Uploading: https://....artifactoryonline.com/.../releases/.../8/...-8.pom
> [INFO] ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO] ------------------------------------------------------------------------
> [INFO] ...
> [INFO] ------------------------------------------------------------------------
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy (default-deploy) on project ...: Failed to deploy artifacts: Could not transfer artifact ...:...:pom:8 from/to ... (https://....artifactoryonline.com/.../releases): Host name may not be null -> [Help 1]
> {code}

--
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