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:[EMAIL PROTECTED] > 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�$��" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > 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: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
