Don't hardcode the project version as the gwt version in the IT tests but reuse
the gwt.version property from the main pom (easy patch attached)
------------------------------------------------------------------------------------------------------------------------------------------------
Key: MGWT-220
URL: http://jira.codehaus.org/browse/MGWT-220
Project: Maven 2.x GWT Plugin
Issue Type: Improvement
Affects Versions: 1.2
Reporter: Geoffrey De Smet
Priority: Minor
Attachments: MGWT-220.patch
In the main pom, we find:
<gwt.version>${project.version}</gwt.version>
which is ok. But if we change the GWT version, different from the pom version,
things start breaking.
For example, this files breaks:
/src/it/async-with-inner-class/pom.xml
This part:
<dependency>
<groupId>com.google.gwt</groupId>
<artifactId>gwt-user</artifactId>
<version>@pom.version@</version> <== problem
<scope>provided</scope>
</dependency>
Should be:
<dependency>
<groupId>com.google.gwt</groupId>
<artifactId>gwt-user</artifactId>
<version>@gwt.version@</version> <== solution
<scope>provided</scope>
</dependency>
The attached patch does that for all occurrences. It's easy to apply and
afterward the "mvn clean install" and all testcases still work, but it's easier
to l et the GWT version differ from the pom version if that's ever needed.
--
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
