I was able to solve this issue by changing the machine name(host name)in the
remote repository list to the IP address.
Didn't quite understand what the issue is, though.
Any ideas ?
Regards,
Kanakambaran
I also said it should be harmless :)
I've successfully used Tomcat as a remote repo in the past. There are
some other things you can try:
- try maven 1.1-beta-1
- try downloading normally (using wget or a browser) from the same URL
- check for errors in the tomcat server logs
Cheers,
Brett
On
Hi,
Downloading normally is possible, that is what we are doing now -
downloading manually and copying to the local repository :) which is
something we do not want to do.
Have checked the tomcat server logs and didn't find any errors.
I tried using mavne1.1-beta-1, am getting another error
Is it possible that you are using a proxy that can't communicate with
tomcat? Preemptive auth should only be used with an authenticating
proxy or basic auth site.
- Brett
On 7/27/05, Kanakambaran Nair [EMAIL PROTECTED] wrote:
Hi,
Downloading normally is possible, that is what we are doing
We do have a proxy but not for machines in the intranet. Also, while trying
to access the same via the browser, it does not ask for any
username/password.
Hi Andrei,
Where did you keep the jars?
You should keep the jars as described in the below structure
User.home\.maven\repository\Groupidname(folder)\jars(folder)\ur .jar
Also you need to add the dependency in your Project.xml file.
Regards
Jayaram
-Original Message-
From: Andrei Szabo
Jars are kept in a remote repository and downloaded
if they are missing from the local repository.
Everything works well, the jars are downloaded and
placed where they should be, in the local repository,
w/ the minor upset caused by the warnings. Still
trying to get rid of them...
Andrei
---
Whatever server you are running is not providing the Last-Modified
header for the URLs (which would generally be the timestamp of the
file on the server's file system).
These are harmless (and probably unnecessary) for non-SNAPSHOT JARs.
It may be a problem for SNAPSHOTs, though I think they will
