Before releasing a mavenized web project plus Vaadin, several problems popped up because the modification of sources made by Vaadin compilations.
Finally the solution was to exclude the problematic part that always is regenerated if it does not exist anyway:
------------------------------------------------------------------------
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-release-plugin</artifactId>
<version>2.5</version>
<configuration>
<providerImplementations>
<svn>javasvn</svn>
</providerImplementations>
<autoVersionSubmodules>true</autoVersionSubmodules>
<tagNameFormat>v@{project.version}</tagNameFormat>
<checkModificationExcludes>
<checkModificationExclude>${project.build.outputDirectory}/**/VAADIN/**</checkModificationExclude>
</checkModificationExcludes>
<configuration>
<preparationGoals>clean verify</preparationGoals>
</configuration>
</configuration>
<dependencies>
<dependency>
<groupId>com.google.code.maven-scm-provider-svnjava</groupId>
<artifactId>maven-scm-provider-svnjava</artifactId>
<version>2.1.1</version>
</dependency>
</dependencies>
</plugin>
------------------------------------------------------------------------
Enjoy!
