You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Marten Deinum (JIRA)" <ji...@codehaus.org> on 2010/04/27 09:33:12 UTC
[jira] Created: (MNG-4647) Upgrade to beta-1 results in 'unmappable
character for encoding UTF-8 -> '
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
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
[jira] Updated: (MNG-4647) Upgrade to beta-1 results in 'unmappable
character for encoding UTF-8 -> '
Posted by "Marten Deinum (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-4647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marten Deinum updated MNG-4647:
-------------------------------
Attachment: build-alpha7.log
File showing build log under alpha-7, notice the success message.
> 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
[jira] Reopened: (MNG-4647) Upgrade to beta-1 results in
'unmappable character for encoding UTF-8 -> '
Posted by "Marten Deinum (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-4647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marten Deinum reopened MNG-4647:
--------------------------------
I still find it strange that the SAME setup works with previous versions, we specified the plugin versions in the pom, but it breaks on beta-1. There is something that changed/broke functional plugins.
The full project encoding is UTF-8
from our parent pom
<project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
So this should be picked up by all plugins even the once that generate sources (which is imho the problem because the complaint is on generated sources not sources written by ourselves.). So my guess is propagating this setting to plugins is broken somehow...
> 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
[jira] Closed: (MNG-4647) Upgrade to beta-1 results in 'unmappable
character for encoding UTF-8 -> '
Posted by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org>.
[ 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
[jira] Issue Comment Edited: (MNG-4647) Upgrade to beta-1 results
in 'unmappable character for encoding UTF-8 -> '
Posted by "Marten Deinum (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-4647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=219075#action_219075 ]
Marten Deinum edited comment on MNG-4647 at 4/27/10 4:38 AM:
-------------------------------------------------------------
File showing build log under alpha-7, notice the success message.
Regarding a working sample, create simple project which uses jax-ws plugin run with alpha-7 success, run with beta-1 fail. This is on a windows 7 system with default settings (so filesystem encoding is Cp1252, see log also).
was (Author: mdeinum):
File showing build log under alpha-7, notice the success message.
> 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
[jira] Closed: (MNG-4647) Upgrade to beta-1 results in 'unmappable
character for encoding UTF-8 -> '
Posted by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org>.
[ 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
bq. <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
This is just a property, there is no magic that makes this picked up by plugins. A plugin has to explicitly support it and spontaneously I didn't see any encoding related parameters for the [jaxws-maven-plugin|https://jax-ws-commons.dev.java.net/jaxws-maven-plugin/] so I don't see how your setup is ever supposed to work independently from the platform encoding.
Unless you can provide a self-contained example project to demonstrate the issue or at least a debug log from a working Maven 3.x build that indicates an actual difference regarding plugin configuration, we can't help you.
> 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
[jira] Commented: (MNG-4647) Upgrade to beta-1 results in
'unmappable character for encoding UTF-8 -> '
Posted by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org>.
[ 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