I just cloned the issue as MRM-738, but it's still reported as duplicate of MRM-674, which it is not IMHO. See comments on MRM-738. This problem occurred at an important client of mine, so I'm not eager to install any snapshot versions there, if I'm not sure the problem is fixed.
tvworks wrote: > > I am using the SNAPSHOT that Brett provided, and MRM-691 seems to be > fixed, but not MRM-632 as I am still seeing that for some artifacts. > > -----Original Message----- > From: greyfairer1 [mailto:[EMAIL PROTECTED] > Sent: Thursday, March 13, 2008 9:20 AM > To: archiva-users@maven.apache.org > Subject: Re: archiva-1.0.2 eta? > > > So, apart from the log file issues, are MR-632 and MRM-691 fixed in the > 1.02-SNAPSHOT release? Or should I build archiva from trunk to check? > > > Brett Porter wrote: >> >> 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. >>> >> >> > > -- > View this message in context: > http://www.nabble.com/archiva-1.0.2-eta--tp15643198p16030511.html > Sent from the archiva-users mailing list archive at Nabble.com. > > > -- View this message in context: http://www.nabble.com/archiva-1.0.2-eta--tp15643198p16039087.html Sent from the archiva-users mailing list archive at Nabble.com.
