[ 
http://jira.codehaus.org/browse/MGWT-113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=190191#action_190191
 ] 

Dean Povey commented on MGWT-113:
---------------------------------

Sorry, a bit trigger happy:

doesNotWork = Contains a backslash \\

generates:

  /**
   * Translated "Contains a backslash \".
   * 
   * @return translated "Contains a backslash \"
   */
  @DefaultMessage("Contains a backslash \")
  @Key("doesNotWork")
  String doesNotWork();

Which does not compile due to an incorrect @DefaultMessage annotation [should 
be: @DefaultMessage("Contains a backslash \\")]

> Backslash in properties file not correctly handled by gwt:18n goal
> ------------------------------------------------------------------
>
>                 Key: MGWT-113
>                 URL: http://jira.codehaus.org/browse/MGWT-113
>             Project: Maven 2.x GWT Plugin
>          Issue Type: Bug
>    Affects Versions: 1.1
>         Environment: windows, jdk 1.6
>            Reporter: Dean Povey
>
> When using the gwt:i18n goal to generate a class from a properties file which 
> contains a string with an escaped backslash, the backslash is not correctly 
> handled by the generator.  For example the following in the properties file:

-- 
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

        

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


Reply via email to