Mailing-List: contact dev-help@archiva.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@archiva.apache.org
Received-SPF: pass (athena.apache.org: domain of mfncooper@gmail.com
 designates 74.125.44.28 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:sender:to:subject:mime-version:content-type
         :x-google-sender-auth;
        b=dJIf2DAqL8jh7OhswVOUal8Khy1vOU6J4+dNhzYs9Zsz9CzGcrvfXnlIuUCoysKANz
         ZVD6h7GWKIE5krn7kKZR+8ooipSYvpkHbcHAscCLOVnFTorcFXM/UpSxiXr76pAOTR6a
         qkBAig9RgGRYaW8+xued0ub7365NUU6X8ARfU=
Message-ID: <16d6c6200811161733x7c121ff0i3453d25f6428b43b@mail.gmail.com>
Date: Sun, 16 Nov 2008 17:33:57 -0800
From: "Martin Cooper" <martinc@apache.org>
Sender: mfncooper@gmail.com
To: dev@archiva.apache.org
Subject: Windows woes
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_29131_8644754.1226885637678"

------=_Part_29131_8644754.1226885637678
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Folks,

I wanted to bring to your attention a bug that I've just filed, because the
root of the problem may be the cause of other issues that people have seen
with Archiva on Windows. You obviously will know better than I do what kinds
of problems have been reported on Windows but not other OSes. I can imagine
that files unintentionally left open could cause a variety of issues,
though.

Here's the bug report (with patch, of course :).

http://jira.codehaus.org/browse/MRM-1004

This one took me a very long time to track down!

--
Martin Cooper

PS - I guess I should file a bug report against Maven, too, but I could use
a pointer to which component includes MavenXpp3Reader, if anyone happens to
know.

------=_Part_29131_8644754.1226885637678--