maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benjamin Bentmann (JIRA)" <>
Subject [jira] Closed: (MNG-4647) Upgrade to beta-1 results in 'unmappable character for encoding UTF-8 -> '
Date Tue, 27 Apr 2010 09:24:12 GMT


Benjamin Bentmann closed MNG-4647.

    Resolution: Not A Bug

bq. <>UTF-8</>
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|] 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:
>             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:
For more information on JIRA, see:


View raw message