Use maven profile to recompile vaadin widgetset #2
In a older post I describe my solution to handle VAADIN/GWT widgetset compilation with maven.
Today I will share some changes to use GWT 2.4 with my solution.
The problem: after GWT compilation a new directory gwt-unitCache exists under the VAADIN directory. I don’t need this 😉
I integrate this workaround in my profile:
<profile> <!-- Updates Vaadin widgetset definitions based on project dependencies --> <id>update-widgetset</id> <activation> <file> <missing>${basedir}/src/main/webapp/VAADIN/widgetsets/</missing> </file> </activation> <build> <plugins> <plugin> <groupId>com.vaadin</groupId> <artifactId>vaadin-maven-plugin</artifactId> <version>1.0.2</version> <executions> <execution> <phase>generate-resources</phase> <goals> <goal>update-widgetset</goal> </goals> </execution> </executions> </plugin> <plugin> <groupId>org.codehaus.mojo</groupId> <artifactId>gwt-maven-plugin</artifactId> <version>2.4.0</version> <configuration> <webappDirectory>${basedir}/src/main/webapp/VAADIN/widgetsets/</webappDirectory> <extraJvmArgs>-Xmx512M -Xss1024k </extraJvmArgs> <deploy>${project.build.directory}/gwt-tmp/</deploy> <soyc>false</soyc> <force>true</force> <strict>true</strict> <style>OBFUSCATED</style> <optimizationLevel>9</optimizationLevel> </configuration> <executions> <execution> <phase>generate-resources</phase> <goals> <goal>resources</goal> <goal>compile</goal> </goals> </execution> </executions> </plugin> <plugin> <!-- workaround for http://code.google.com/p/google-web-toolkit/issues/detail?id=6397 --> <artifactId>maven-clean-plugin</artifactId> <version>2.4.1</version> <configuration> <filesets> <fileset> <directory>${basedir}/src/main/webapp/VAADIN/</directory> <includes> <directory>gwt-unitCache/**</directory> </includes> <followSymlinks>false</followSymlinks> </fileset> </filesets> <excludeDefaultDirectories>true</excludeDefaultDirectories> </configuration> <executions> <execution> <id>default</id> <phase>generate-resources</phase> <goals> <goal>clean</goal> </goals> </execution> </executions> </plugin> </plugins> </build> </profile>
🙂
Antworten
Du musst angemeldet sein, um einen Kommentar abzugeben.