Mailing-List: contact dev-help@forrest.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@forrest.apache.org
Received-SPF: pass (nike.apache.org: domain of williamstw@gmail.com designates
 74.125.83.48 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type:content-transfer-encoding;
        b=XGM68pZq/7+z9BbLw7XR7tlsVtUvxGfrhFdlH/4h3wJLahYLQN80UFgjmce9V9451J
         Q4ZX3O0SQcnNDksFa142LAxB2+0TOEGSXSnSGB6gsXd5bDzY5BMNb4oYe2ZOz5N2desJ
         1TPpbHzd8XJzpS7Pu68NAZyB65Q6WajesjdbU=
MIME-Version: 1.0
In-Reply-To: <u2u499888441004050404n7cea2fc3gd2735668b79bd75a@mail.gmail.com>
References: <201004010607.o3167I4D004104@forrest.zones.apache.org>
	 <20100401072755.GA44645@igg.local>
	 <m2u499888441004020522hf5ac7004zd71b788bf512501e@mail.gmail.com>
	 <w2j499888441004020613y9e1ddaccm874c8d71ae5e8270@mail.gmail.com>
	 <003101cad4a1$910e0a00$b32a1e00$@com.au>
	 <g2j499888441004050250i9e8f3b9dne6181fd7bdbd64e@mail.gmail.com>
	 <004401cad4ac$d7d849e0$8788dda0$@com.au>
	 <u2u499888441004050404n7cea2fc3gd2735668b79bd75a@mail.gmail.com>
Date: Mon, 5 Apr 2010 07:13:53 -0400
Message-ID: <u2y499888441004050413xdf6a516eqe78d3326708395fc@mail.gmail.com>
Subject: Re: forrest-sample-2 FAILED and build test failed: Could not resolve
	locationmap location
From: Tim Williams <williamstw@gmail.com>
To: dev@forrest.apache.org
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

On Mon, Apr 5, 2010 at 7:04 AM, Tim Williams <williamstw@gmail.com> wrote:
> On Mon, Apr 5, 2010 at 6:43 AM, Gav... <gavin@16degrees.com.au> wrote:
>>
>>
>>> -----Original Message-----
>>> From: Tim Williams [mailto:williamstw@gmail.com]
>>> Sent: Monday, 5 April 2010 7:51 PM
>>> To: dev@forrest.apache.org
>>> Subject: Re: forrest-sample-2 FAILED and build test failed: Could not
>>> resolve locationmap location
>>>
>>> On Mon, Apr 5, 2010 at 5:22 AM, Gav... <gavin@16degrees.com.au> wrote:
>>> >
>>> >
>>> >> -----Original Message-----
>>> >> From: Tim Williams [mailto:williamstw@gmail.com]
>>> >> Sent: Friday, 2 April 2010 11:13 PM
>>> >> To: dev@forrest.apache.org
>>> >> Subject: Re: forrest-sample-2 FAILED and build test failed: Could
>>> not
>>> >> resolve locationmap location
>>> >>
>>> >> On Fri, Apr 2, 2010 at 8:22 AM, Tim Williams <williamstw@gmail.com>
>>> >> wrote:
>>> >> > On Thu, Apr 1, 2010 at 3:27 AM, David Crossley
>>> <crossley@apache.org>
>>> >> wrote:
>>> >> >>> Automated build for forrest-sample-2 FAILED
>>> >> >>> =A0 =A0 =A0[java]
>>> >> >>> =A0 =A0 =A0[java]
>>> >> >>> =A0 =A0 =A0[java] X [0]
>>> linkmap.html
>>> >> =A0 =A0BROKEN: Could not resolve locationmap location.
>>> >> >>
>>> >> >>
>>> >> >> I get that same error doing 'build.sh test' locally.
>>> >> >>
>>> >> >> The build of this Dispatcher sample were okay on the
>>> >> >> zone server before today.
>>> >> >
>>> >> > I'm getting the same thing. =A0It looks like a mounted locationmap
>>> >> can't
>>> >> > be resolved but it appears to be dispatcher-related code. =A0I don=
't
>>> >> > know that code at all but a quick look seems like the resolver
>>> field
>>> >> > in the child class (RecursiveDirectoryTraversalAction) is hiding
>>> the
>>> >> > intended resolver in the parent class (AbstractTraversal). =A0 Can
>>> you
>>> >> > comment out the child class' resolver field and see if that helps?
>>> >> =A0It
>>> >> > seems to get me past that one but then introduces tons of other
>>> >> > "Invalid byte 1 of 1-byte UTF-8 sequence" errors. =A0The timing
>>> seems
>>> >> > right too, =A0it would have been introduced with r929463.
>>> >>
>>> >> I went ahead and applied that because I feel sure that's the right
>>> >> thing to do. =A0I'm now getting errors like:
>>> >>
>>> >> [Fatal Error] :6:25: Invalid byte 1 of 1-byte UTF-8 sequence.
>>> >> X [0] =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 linkmap.pdf BROKEN:
>>> Invalid
>>> >> byte 1 of 1-byte UTF-8 sequence.
>>> >>
>>> >> ... for every pdf file. =A0I don't have time to look into that one
>>> right
>>> >> now though, can someone see if they get the same?
>>> >
>>> > Yes, I am getting it too, but here we are again, a Windows only bug
>>> it
>>> > seems. I don=92t get this on any linux box - which is why our zone
>>> doesn=92t
>>> > complain.
>>>
>>> Actually, I'm on a Mac.
>>
>> fine, cant help then.
>
> Thanks Gav,
> You may have, I think the default encoding on a Mac isn't utf-8
> either. =A0I wonder if our source docs which claim utf-8 encoding,
> aren't? =A0When I get home I'll try to open them in a text editor and
> explicitly save one of the known failing docs with utf-8 encoding and
> see if that helps. =A0Unless, of course, someone happens to have time to
> do this test sooner:)

Firefox does think that my random sampling of content from our svn are
ISO-8859-1 encoded and not UTF-8 (which the xml declaration claims) -
this may be the problem?

--tim