Some (build) targets are incorrectly relying on the platform default encoding

[GoogleCodeExporter]

Some targets are incorrectly relying on the platform default (file) encoding.
In case the user building ZAP doesn't have the platform default encoding set to 
UTF-8 (or ISO-8859-1) it may encounter build errors, like:
[...]: error: unmappable character for encoding [...]

Those targets should be changed to not rely on the platform default encoding 
and use always the same (UTF-8).

The targets that need to be changed are:
Project zaproxy:
 - "compile" (trunk);
 - "generate-javadocs" (trunk);
Project zap-extensions:
 - "compile" (alpha and beta branches and trunk).

Original issue reported on code.google.com by THC...@gmail.com on 27 Mar 2013 at 7:30

[GoogleCodeExporter]

r3000

Original comment by THC...@gmail.com on 27 Mar 2013 at 7:40

• Changed state: Committed

[GoogleCodeExporter]

https://code.google.com/p/zap-extensions/source/detail?r=407

Original comment by THC...@gmail.com on 27 Mar 2013 at 7:45

[GoogleCodeExporter]

Original comment by psii...@gmail.com on 2 Apr 2013 at 9:47

• Added labels: Build-20130402

[GoogleCodeExporter]

Issue 571 has been merged into this issue.

Original comment by THC...@gmail.com on 8 Apr 2013 at 4:05

[GoogleCodeExporter]

Fixed in 2.1.0

Original comment by psii...@gmail.com on 18 Apr 2013 at 9:49

• Changed state: Fixed