Still, +1 on dropping the source back to ASCII. On Thu, Jan 6, 2011 at 11:26 AM, James Purser <[email protected]>wrote:
> yup and just confirmed it, problem was PEBKAC. > > James > > On Thu, Jan 6, 2011 at 11:22 AM, James Purser <[email protected] > >wrote: > > > It looks like a system problem as opposed to WIAB. > > > > James > > > > > > On Thu, Jan 6, 2011 at 11:19 AM, David Hearnden <[email protected] > >wrote: > > > >> James, which OS / JDK version? > >> > >> It's building fine for me. Java is meant to allow unicode in comments. > >> > >> -Dave > >> > >> > >> On Thu, Jan 6, 2011 at 11:06 AM, Brett Morgan <[email protected]> > >> wrote: > >> > does java deal with utf8 in source code these days? > >> > > >> > On Thu, Jan 6, 2011 at 10:45 AM, James Purser <[email protected] > >> >wrote: > >> > > >> >> Is anyone else getting a build failure on the tip? > >> >> > >> >> compile-tests: > >> >> [javac] Compiling 414 source files to > >> >> /home/purserj/wave-protocol/build/test > >> >> [javac] > >> >> > >> >> > >> > /home/purserj/wave-protocol/test/org/waveprotocol/wave/federation/xmpp/RemoteDiscoTest.java:34: > >> >> warning: unmappable character for encoding ASCII > >> >> [javac] * Performs na??ve tests over RemoteDisco. Integration > >> testing > >> >> is performed in > >> >> [javac] ^ > >> >> [javac] > >> >> > >> >> > >> > /home/purserj/wave-protocol/test/org/waveprotocol/wave/federation/xmpp/RemoteDiscoTest.java:34: > >> >> warning: unmappable character for encoding ASCII > >> >> [javac] * Performs na??ve tests over RemoteDisco. Integration > >> testing > >> >> is performed in > >> >> [javac] ^ > >> >> [javac] error: warnings found and -Werror specified > >> >> [javac] 1 error > >> >> > >> >> James > >> >> > >> > > >> > > >> > > >> > -- > >> > Brett Morgan > >> > http://www.google.com/profiles/brett.morgan > >> > > >> > > > > > -- Brett Morgan http://www.google.com/profiles/brett.morgan
