[
http://jira.codehaus.org/browse/MGWT-67?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=177228#action_177228
]
Felipe desiderati commented on MGWT-67:
---------------------------------------
This bug doesn´t occur anymore in the new version of the plugin.
Basicly speaking, if you just have declared the <i18nConstantsBundle> tag, the
error described above will occur. See configuration that triggers the error:
<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>gwt-maven-plugin</artifactId>
<version>1.0-SNAPSHOT</version>
<executions>
<execution>
<goals>
<goal>i18n</goal>
</goals>
</execution>
</executions>
<configuration>
<i18nConstantsBundle>com.mycompany.gwt.Bundle1</i18nConstantsBundle>
</configuration>
</plugin>
BUT, if you instead have used <i18nMessagesBundle>, the plugin will execute
without any errors.
> Problem using i18n goal
> -----------------------
>
> Key: MGWT-67
> URL: http://jira.codehaus.org/browse/MGWT-67
> Project: Maven 2.x GWT Plugin
> Issue Type: Bug
> Affects Versions: 1.1
> Environment: Maven 2.0.9
> Reporter: Felipe desiderati
>
> If you only declare the <i18nConstantsBundle> tag inside the plugin
> configuration, the following error occurs:
> Reason: neither i18nConstantsBundles, i18nMessagesBundles nor
> i18nConstantsWithLookupBundles present, cannot execute i18n goal
> But if you chage the configuration to use the <i18nMessagesBundle> tag
> instead, plugin will executes without any errors.
--
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
