On Mon, 2003-10-27 at 06:41, Edmund Urbani wrote:Thanks for the quick fix. It works fine now - at least on my system (a colleage of mine still has trouble getting maven to work with Win2000, but that's a totally different problem - this list might see a mail about it soon). I'm glad I could get rid of that ugly workaround now.
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.
Fixed in CVS HEAD. You might want to try it yourself, I don't do Maven
work until the evening so I won't bootstrap until then but I believe
I've isolated the problem.
Edmund
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
