Hello cn73! Thanks for your reply, as it was very helpful. I fixed the problem taking your hint. You are right and it was a splendid idea. I figured (from the previous link you sent me) that the problem was (the problem of the guy in that specific thread) was an encoding problem. And although i looked at my POM several times, i always missed the fact that there was 1 encoding tag already. So i never thought the problem could be about the same. Thanks mate, you reply was very usefull. I went looking for some more information and i found the following: http://docs.codehaus.org/display/MAVENUSER/POM+Element+for+Source+File+Encoding where it clearly says that changing the encoding for some plugins (especially build plugins) can have a huge impact. And then the pieces of the puzzle somewhat started to connect in my head. here is the troublesome piece of POM: <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-compiler-plugin</artifactId> <configuration> <source>1.6</source> <target>1.6</target> <maxmem>128m</maxmem> <encoding>ISO-8859-1</encoding> </configuration> </plugin> This was the only plugin (of 3 defined plugins) that had an encoding tag to explicitly set an encoding. Now, i dont know what the default is, but i bet it is UTF-8. So i put the encoding to ISO-8859-1 for all of the defined plugins (being: maven-compiler-plugin, maven-resources-plugin (also build plugin) and jasperreports-maven-plugin (not a build plugin, but very important one considering my goals). I did a clean and build again (in netbeans), relaunched the project and hooray, it works like a charm now. Thanks for the fast replies! Ocketje