[
http://jira.codehaus.org/browse/MNG-4647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann closed MNG-4647.
----------------------------------
Resolution: Not A Bug
Assignee: Benjamin Bentmann
The relevant part of your build log:
{noformat}
[DEBUG] Configuring mojo
'org.apache.maven.plugins:maven-compiler-plugin:2.3:compile' with basic
configurator -->
[DEBUG] (f) encoding = UTF-8
[DEBUG] -- end configuration --
...
[ERROR]
\repositories\repos_defacto\defacto\defacto-service\src\main\generated-source\nl\famed\defacto\clearing\vecozo\clearing\ElektronischDeclareren.java:[23,43]
unmappable character for encoding UTF-8
{noformat}
For one, the error is raised by the Maven Compiler Plugin and not Maven itself.
Second, the error is appropriate, if you configure the source encoding to UTF-8
but your source files don't match. So you need to either fix your source files
or specify the proper encoding for the compiler.
> Upgrade to beta-1 results in 'unmappable character for encoding UTF-8 -> '
> --------------------------------------------------------------------------
>
> Key: MNG-4647
> URL: http://jira.codehaus.org/browse/MNG-4647
> Project: Maven 2 & 3
> Issue Type: Bug
> Affects Versions: 3.0-beta-1
> Reporter: Marten Deinum
> Assignee: Benjamin Bentmann
> Attachments: build.log
>
>
> Using maven 3 alpha 7 my project builds fine, after upgrading to beta-1 it
> stops with the mentioned exception. Reverting to alpha-7 or 2.0.11 seems to
> fix the issue. Looks like a regression bug to me.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
