[
http://jira.codehaus.org/browse/MNG-4647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=219080#action_219080
]
Benjamin Bentmann commented on MNG-4647:
----------------------------------------
>From the 3.0-beta-1 log:
{noformat}
[INFO] --- maven-compiler-plugin:2.3:compile (default-compile) @
defacto-service ---
{noformat}
Form the 3.0-alpha-7 log:
{noformat}
[INFO] --- maven-compiler-plugin:2.0.2:compile (default-compile) @
defacto-service ---
{noformat}
i.e. you haven't locked down the version of the Compiler Plugin, hence your
build is subject to environmental issues like the default plugin version
provided by Maven.
In more detail, your build is affected by MCOMPILER-70 which made the Compiler
Plugin 2.1+ recognize the project.build.sourceEncoding property. Maven Compiler
Plugin 2.0.2 defaults to the platform encoding, apparently matching the
encoding used by jaxws thereby making your build pass by the mere fact that the
specified encoding of UTF-8 is ignored by the two plugins.
> 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-alpha7.log, 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
