It's hard to tell if it is actually hitting Archiva and where the problem might be.
Some more things to try: - enable debug logging in Archiva (edit apps/archiva/webapp/WEB-INF/classes/log4j.xml) - are you using a http proxy in maven? - what version of Archiva are you using? Cheers, Brett 2008/6/6 Danilo Tuler <[EMAIL PROTECTED]>: > > > > Brett Porter wrote: >> >> It is definitely receiving a 404. Is there anything in the Archiva >> logs to indicate why? >> > > Nothing in audit.log or archiva.log. > > > Brett Porter wrote: >> >> You said you were able to retrieve the JAR - but are you also able to >> retrieve the POM that it is unable to find? >> > > Yes. The url I open is: > > http://localhost:8080/archiva/repository/internal/org/apache/maven/plugins/maven-clean-plugin/2.2/maven-clean-plugin-2.2.pom > > -- > View this message in context: > http://www.nabble.com/Starting-from-scratch-tp13229503p17682831.html > Sent from the archiva-users mailing list archive at Nabble.com. > > -- Brett Porter Blog: http://blogs.exist.com/bporter/
