[
http://jira.codehaus.org/browse/MGWT-290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=265333#action_265333
]
Maximiliano Carrizo commented on MGWT-290:
------------------------------------------
Olivier, this behavior still happens with GWT-Maven plugin 2.2.0
> CLONE -Maven resource filtering should work for resources used by the GWT
> plugin
> --------------------------------------------------------------------------------
>
> Key: MGWT-290
> URL: http://jira.codehaus.org/browse/MGWT-290
> Project: Maven 2.x GWT Plugin
> Issue Type: Bug
> Affects Versions: 1.2
> Reporter: Maximiliano Carrizo
> Assignee: Olivier Lamy
> Fix For: 2.1.0-1
>
>
> We have public interface BuildConstants extends ConstantsWithLookup
> which has a String projectVersion();
> The property file src/main/filtered-resources/.../BuildConstants.properties
> contains projectVersion=${pom.version}
> The pom.xml contains the necessary plumbing:
> <build>
> <resources>
> <resource>
> <directory>src/main/resources</directory>
> </resource>
> <resource>
> <directory>src/main/filtered-resources</directory>
> <filtering>true</filtering>
> </resource>
> </resources>
> ...
> After I run "mvn clean install" the file
> target.classes/.../BuildConstants.properties
> contains projectVersion=5.2.0-SNAPSHOT
> yes in the GWT application "mvn gwt:run" it still shows ${pom.version}
> because the GWT compiler is run with src/main/resources instead of
> target/classes apparently.
> Relates to MGWT-216.
--
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
