add an "encoding" parameter for source files and use ${project.build.sourceEncoding} as default value

like explained in MJNCSS-15, encoding support in javancss itself is needed first

This will make the forceEncoding option redundant, or I miss something ?

see http://mojo.codehaus.org/javancss-maven-plugin/report-mojo.html#forceEncoding

forceEncoding option will be replaced by sourceEncoding (or simply encoding if you prefer)
forceEncoding should never have existed: XML files provide their encoding inside the stream, then you don't need to force anything if the XML stream is valid (which is not the case actually)

This will make the forceEncoding option redundant, or I miss something ?

If the employed SAXReader is really not capable of detecting the file encoding from the XML declaration, the plugin should simply use WriterFactory.newXmlReader() from plexus-utils and pass the reader to SAXReader.read(Reader).

I agree with Hervé, the parameter forceEncoding should be removed. Deleting mojo parameters shouldn't cause any harm with backward-compat, IIRC Maven silently ignore configuration elements from the POM for which no corresponding setter/field exists on the mojo.

Thanks !

Let's see what the guys at javancss will do.

FYI, project created on Codehaus

done in r9784