You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by Jå$òñ Må¢þhè®$õñ <Ma...@byu.edu> on 2004/03/24 16:14:56 UTC
HTTPS bug? / workaround
Ive setup a remote repository using https
~/build.properties
maven.repo.remote=https://myServer.edu/maven,http://www.ibiblio.org/mave
n
Using this setup causes maven to search for dependencies using only one
slash.
Maven output:
Error retrieving artifact from [https:/myServer.edu/maven/....]
The work around appears to be to use three slashes in my
build.properties.
maven.repo.remote=https:///myServer.edu/maven
Is this a bug? Or is maven supposed to behave this manner?
--Jâsõñ Mà©þh뮧òñ
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
RE: HTTPS bug? / workaround
Posted by Age Mooy <am...@home.nl>.
It is a bug in the RC1 DependencyVerifier, it was fixed in RC2 a long time ago. We also have an https repo and until today we used a
patched version of RC1.
I've double-checked it today and this bug is no longer in the RC2 release.
Age
> -----Original Message-----
> From: Emmanuel Venisse [mailto:emmanuel@venisse.net]
> Sent: Wednesday, March 24, 2004 16:36 PM
> To: Maven Developers List
> Subject: Re: HTTPS bug? / workaround
>
>
> It's a bug. Could you add an issue in Jira?
>
> Emmanuel
>
> ----- Original Message -----
> From: "Jå$òñ Må¢þhè®$õñ" <Ma...@byu.edu>
> To: <de...@maven.apache.org>
> Sent: Wednesday, March 24, 2004 4:14 PM
> Subject: HTTPS bug? / workaround
>
>
> I've setup a remote repository using https
>
> ~/build.properties
> maven.repo.remote=https://myServer.edu/maven,http://www.ibibli
> o.org/mave
> n
>
> Using this setup causes maven to search for dependencies
> using only one
> slash.
> Maven output:
> Error retrieving artifact from [https:/myServer.edu/maven/....]
>
>
> The work around appears to be to use three slashes in my
> build.properties.
> maven.repo.remote=https:///myServer.edu/maven
>
> Is this a bug? Or is maven supposed to behave this manner?
>
> --Jâsõñ Mà©þh뮧òñ
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: HTTPS bug? / workaround
Posted by Emmanuel Venisse <em...@venisse.net>.
It's a bug. Could you add an issue in Jira?
Emmanuel
----- Original Message -----
From: "Jå$òñ Må¢þhè®$õñ" <Ma...@byu.edu>
To: <de...@maven.apache.org>
Sent: Wednesday, March 24, 2004 4:14 PM
Subject: HTTPS bug? / workaround
I've setup a remote repository using https
~/build.properties
maven.repo.remote=https://myServer.edu/maven,http://www.ibiblio.org/mave
n
Using this setup causes maven to search for dependencies using only one
slash.
Maven output:
Error retrieving artifact from [https:/myServer.edu/maven/....]
The work around appears to be to use three slashes in my
build.properties.
maven.repo.remote=https:///myServer.edu/maven
Is this a bug? Or is maven supposed to behave this manner?
--Jâsõñ Mà©þh뮧òñ
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org