Well, this is the same error that I was seeing before, "invalid path". However, am not sure if these particular artifacts failed before, after, or both before and after your changes.
The performance/stability seems ok, but it has only been a single day to this point. I would like to do some longer testing in that area. -----Original Message----- From: Brett Porter [mailto:[EMAIL PROTECTED] Sent: Tuesday, February 26, 2008 1:58 PM To: archiva-users@maven.apache.org Subject: Re: archiva-1.0.2 eta? Are these issues new, or were they present before (just wondering if it's a regression because of my changes). Anyway, I can add more tests. How is the performance/stability after a little while now? - Brett On 27/02/2008, Jason Chaffee <[EMAIL PROTECTED]> wrote: > Looks like I still have some issues. I have attached parts of the log > file because the entire file is too large. Let me know if you would > like any other information. I am using the same archiva.xml as before. > These errors may be due to some non-standard artifacts in our repo, but > most of them do seem correct to me. I do know that we have some > artifacts that do not have poms though. >
