[
http://jira.codehaus.org/browse/MGWT-285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=269272#action_269272
]
jieryn commented on MGWT-285:
-----------------------------
+1 month and this problem is still hitting a lot of users. The intricacies of
Maven classpath munging are beyond my abilities.. what can I do to help this
problem get resolved?
I really want this to be resolved because I maintain lots of .gwt.xml files
which are twinned for production and development modes (e.g. setting GWT
j.u.logging to different levels) and it would be nice to simply reference a
variable in my exploiting project's .gwt.xml for the <inherits
name="com.acme.base.gwt.Logging-${env}"/> where ${env} is set by default for
production and overridden via profile for development.
> Filtered resource files are not used to create generated sources
> ----------------------------------------------------------------
>
> Key: MGWT-285
> URL: http://jira.codehaus.org/browse/MGWT-285
> Project: Maven 2.x GWT Plugin
> Issue Type: Bug
> Affects Versions: 2.1.0-1, 2.2.0
> Reporter: Benjamin Peter
> Attachments: MGWT-285.zip
>
>
> Hello,
> when I use filtered resources for messages or constant files in my maven gwt
> project it seems like the original source .properties files are used instead
> of the filtered ones from the target directory.
> As far as I can see it, I have the same problem as MGWT-216 which seems to be
> closed. But it does not work for me in 2.1.0-1 or 2.2.0.
> Example:
> Following command is executed by the maven gwt plugin:
> /usr/lib/jvm/java-6-sun-1.6.0.22/jre/bin/java -Xmx512m -classpath
> PROJECTPATH/src/main/java:PROJECTPATH/src/main/resources:PROJECTPATH/target/admingui/WEB-INF/classes:HOME/.m2/repository/com/google/gwt/gwt-user/2.1.1/gwt-user-2.1.1.jar:HOME/.m2/repository/com/google/gwt/inject/gin/1.0/gin-1.0.jar:HOME/.m2/repository/com/google/inject/guice/2.0/guice-2.0.jar:HOME/.m2/repository/aopalliance/aopalliance/1.0/aopalliance-1.0.jar:HOME/.m2/repository/com/google/code/gwt-log/gwt-log/3.0.2/gwt-log-3.0.2.jar:HOME/.m2/repository/com/extjs/gxt/2.2.0/gxt-2.2.0.jar:HOME/.m2/repository/log4j/log4j/1.2.16/log4j-1.2.16.jar:HOME/.m2/repository/com/google/gwt/gwt-user/2.1.1/gwt-user-2.1.1.jar:HOME/.m2/repository/com/google/gwt/gwt-dev/2.1.1/gwt-dev-2.1.1.jar
> com.google.gwt.i18n.tools.I18NSync -out
> PROJECTPATH/target/generated-sources/gwt namespace.client.constants.Version
> What works is the following, without PROJECTPATH/src/main/resources maybe it
> even should be without PROJECTPATH/src/main/java:
> /usr/lib/jvm/java-6-sun-1.6.0.22/jre/bin/java -Xmx512m -classpath
> PROJECTPATH/src/main/java:PROJECTPATH/target/admingui/WEB-INF/classes:HOME/.m2/repository/com/google/gwt/gwt-user/2.1.1/gwt-user-2.1.1.jar:HOME/.m2/repository/com/google/gwt/inject/gin/1.0/gin-1.0.jar:HOME/.m2/repository/com/google/inject/guice/2.0/guice-2.0.jar:HOME/.m2/repository/aopalliance/aopalliance/1.0/aopalliance-1.0.jar:HOME/.m2/repository/com/google/code/gwt-log/gwt-log/3.0.2/gwt-log-3.0.2.jar:HOME/.m2/repository/com/extjs/gxt/2.2.0/gxt-2.2.0.jar:HOME/.m2/repository/log4j/log4j/1.2.16/log4j-1.2.16.jar:HOME/.m2/repository/com/google/gwt/gwt-user/2.1.1/gwt-user-2.1.1.jar:HOME/.m2/repository/com/google/gwt/gwt-dev/2.1.1/gwt-dev-2.1.1.jar
> com.google.gwt.i18n.tools.I18NSync -out
> PROJECTPATH/target/generated-sources/gwt namespace.client.constants.Version
> Looking at the plugin source it seems the whole compile classpath is used to
> build the messages files, maybe a different classpath should be used here. I
> fear I don't have enough knowledge to make those changes myself but I guess
> shell/I18NMojo.java and AbstractGwtMojo.java maybe with SCOPEs are involved.
--
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
