forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gavin <ga...@16degrees.com.au>
Subject RE: Can't get Dispatcher working at all windows/linux from trunk
Date Tue, 23 Feb 2010 02:28:07 GMT
On Tue, 2010-02-23 at 10:48 +1000, Gav... wrote:
> 
> > -----Original Message-----
> > From: Thorsten Scherler
> > [mailto:thorsten.scherler.ext@juntadeandalucia.es]
> > Sent: Monday, 22 February 2010 10:26 PM
> > To: gavin@16degrees.com.au
> > Subject: RE: Can't get Dispatcher working at all windows/linux from
> > trunk
> > 
> 
> <snip>
> 

> > >
> > > I also tested in 1.6 and get the following compile errors:
> > >
> > > compile:
> > > Created dir: /home/gmcdonald/asf/forrest/build/classes
> > > Compiling 33 source files to
> > /home/gmcdonald/asf/forrest/build/classes
> > >
> > /home/gmcdonald/asf/forrest/main/java/org/apache/forrest/util/IdGenerat
> > orTransformer.java:177: unmappable character for encoding UTF8
> > >                 //	- <a href="#Quelques+r%E8gles...">Quelques
> > > r�gles...</a
> > >                   	                                            ^
> > >
> > /home/gmcdonald/asf/forrest/main/java/org/apache/forrest/util/IdGenerat
> > orTransformer.java:180: unmappable character for encoding UTF8
> > >                 //	- <a href="#Quelques+r%C3%A8gles...">Quelques
> > > r�gles...</a>
> > >
> > ^
> > > 2 errors
> > >
> > > So, getting closer to having 1.6 work too.
> > 
> > Hmm, that is under Windows right?
> > 
> > I have seen it before in other projects.
> 
> actually no, that was under Linux (using java 1.6.0_15-b03)

Having tested further, this error is nothing to do with dispatcher.

We have some comments in IdGeneratorTransformer.java :

// Use of the new version of encode method to avoid to generate URI such
as :
//- <a href="#Quelques+r%E8gles...">Quelques règles...</a>
//  Which is not, curiously, well decoded...
//  The new methode - which allow to specify "UTF-8" gives :
//- <a href="#Quelques+r%C3%A8gles...">Quelques règles...</a>
// And it works OK,


If I remove those comments from the file then I get it to pass on Java
1.6 on linux too, so I have it working in all javas on windows/linux
now.

I have no idea why the windows compiler ignores those chars and compiles
fine when the linux one didnt like them.

However, I;d suggest just removing those comments from the java file and
putting them in the generated docs or a faq somewhere instead.

Thoughts?

Gav...



Mime
View raw message