Grails

No native2ascii be executed when "grails war"

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 0.5.6
  • Fix Version/s: 0.6
  • Component/s: None
  • Labels:
    None
  • Environment:
    grails 0.5.6 & JDK1.5.0_12-b04

Description

When I package my app to war(by "grails war") and deploy to tomcat , I found the properties files in WEB-INF/grails/i18n folder have NO be encode by natice2ascii causing wildly pages

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Graeme Rocher added a comment -

Its is a config option http://grails.org/Config

Show
Graeme Rocher added a comment - Its is a config option http://grails.org/Config
Hide
Permalink
Florian Lindauer added a comment -

Sorry, but is this config option really the solution to this problem?
I created a Config.groovy with this option, it did not help. With or without it, the native2ascii runs on calling the "war" target,
converting the messages from source grails-app/i18n to target WEB-INF/grails-app/i18n/ directory of the project space.
But in the .war the original messages.properties is found - not the transformed one.

Show
Florian Lindauer added a comment - Sorry, but is this config option really the solution to this problem? I created a Config.groovy with this option, it did not help. With or without it, the native2ascii runs on calling the "war" target, converting the messages from source grails-app/i18n to target WEB-INF/grails-app/i18n/ directory of the project space. But in the .war the original messages.properties is found - not the transformed one.
Hide
Permalink
Graeme Rocher added a comment -

There is a separate bug where native2ascii doesn't work with war files, we'll be addressing that over the next few days

Show
Graeme Rocher added a comment - There is a separate bug where native2ascii doesn't work with war files, we'll be addressing that over the next few days
Hide
Permalink
Florian Lindauer added a comment -

We upgraded to 0.6 now, and it works (just to confirm fix_version)
(Of course, Config.groovy was not supported in 0.5.6 at all, but the config option was not the problem)
Thanks!

Show
Florian Lindauer added a comment - We upgraded to 0.6 now, and it works (just to confirm fix_version) (Of course, Config.groovy was not supported in 0.5.6 at all, but the config option was not the problem) Thanks!

People

Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved:
Atlassian JIRA (v4.4.1#660-r161644) | Report a problem
Powered by a free Atlassian JIRA open source license for Grails project. Try JIRA - bug tracking software for your team.