Hi Edmund,

please report the bug to JIRA.

http://maven.apache.org/issue-tracking.html

Thanks,
Martin

On Mon, 2003-10-27 at 12:41, Edmund Urbani wrote:
> Has anybody every tried to let maven resolve dependencies by letting it 
> download artifacts via https?
> 
> I added this line to my build.properties
> maven.repo.remote=https://repository.liland.org:21/maven
> (don't bother trying to connect there. you can't without the certificate 
> and private key, that you don't have)
> 
> However maven keeps getting java.net.ConnectExceptions trying to access 
> "https:/repository.liland.org:21/maven". Note that there is only 1 slash 
> after "https:" (!!)
> 
> If i modify the line in build.properties like this
> maven.repo.remote=https:///repository.liland.org:21/maven
> it works fine
> 
> maven-1.0-rc1 keeps dropping one of the slashes for some reason
> 
> I hope the next release fixes this. Till then I'll probably use the 
> "///"-workaround.
> 
>  Edmund
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
-- 
Martin Skopp
Riege Software International GmbH
Support: mailto:[EMAIL PROTECTED], Information: http://www.riege.com
 
This email is intended to be viewed with a nonproportional font.
Public Key on http://www.keyserver.net, Key-ID: 3D4027B5
Fingerprint: 1970 C78D 9A1D 99FA 5CE4  5C0D 29E6 6A95 3D40 27B5



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to