Hello Vincent, >From what I've seen [ I'm no expert ;-) ] you need to have web read rights on the folders on the server, not just the artifacts. I.e. in your case, putting 'http://<server>/maven2-repos/myrepo2/' above in a browser should provide listing on contents (as well as for sub-folders), instead of just being able to download the xml file...
Another possible reason could be proxy configuration in your settings.xml file, i.e. the visibility of the server _from_ where you're starting mvn. HTH, w On Wed, Nov 26, 2008 at 4:45 PM, vbehar <[EMAIL PROTECTED]> wrote: > > > Wayne Fay wrote: > > > > This is generally caused by incorrectly configured webservers running > > at the mirrors you are connecting to. > > > > It needs to send a real 404. Not just an error message that looks like a > > 404. > > > > I've already checked, and our webserver is well configured. > As you can see in the file, maven writes the HTTP headers response, and > there is : > HTTP/1.1 404 Not Found > > Thanks anyway for the answer > -- > View this message in context: > http://www.nabble.com/metadata-download-and-404-tp20699722p20703491.html > Sent from the Maven - Users mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
