"widgetset version 7.0.1 does not seem to match theme version"

Hello,
I want to do a new custom theme called “main-theme”.I am testing a new project built from vaadin 7 archetype with no added dependencies
Also i have the correct main-theme.scss with following content:

@import “…/reindeer/reindeer.scss”;

@mixin main-theme {
/* Include all the styles from the reindeer theme */
@include reindeer;
}

Also, styles.scss with content:
@import “scss/main-theme.scss”;

@include main-theme;

But when i use this custom theme, with @Theme(“main-theme”) in my entry class, reindeer buttons are not shown correctly (only the caption is shown).If i dont have @Theme set, Button´s are rendered correctly

When i use “?debug” for this custom theme , the warning “widgetset version 7.0.1 does not seem to match theme version” apeears always.
I already confirmed if the widgeset were compiled with 7.0.1 and it seems they are.

This only happens if i use scss.If i use the styles.css with legacy reindeer it works correctly

I think the rendered is not ok due to this warning.
Can you please help me?

My dependencies are:

vaadin-server-7.0.1.jar
vaadin-shared-7.0.1.jar
vaadin-shared-deps-1.0.2.jar
vaadin-theme-compiler-7.0.1.jar
commons-jexl-2.1.1.jar
commons-logging-1.1.1.jar
sac-1.3.jar
cssparser-0.9.5.jar
commons-cli-1.2.jar
jsoup-1.6.3.jar
vaadin-themes-7.0.1.jar
servlet-api-2.4.jar

My pom.xml is:

<?xml version="1.0" encoding="UTF-8"?>


4.0.0
com.test/groupId>
test-application/artifactId>
war
1.0.0-SNAPSHOT
Vaadin Web Application

<properties>
	<project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
	<vaadin.version>7.0.1</vaadin.version>
	<vaadin.plugin.version>${vaadin.version}</vaadin.plugin.version>
</properties>
<repositories>
	<repository>
		<id>vaadin-addons</id>
		<url>http://maven.vaadin.com/vaadin-addons</url>
	</repository>
	<repository>
		<id>vaadin-snapshots</id>
		<url>http://oss.sonatype.org/content/repositories/vaadin-snapshots/</url>
		<releases>
			<enabled>false</enabled>
		</releases>
		<snapshots>
			<enabled>true</enabled>
		</snapshots>
	</repository>
</repositories>
<pluginRepositories>
	<pluginRepository>
		<id>vaadin-snapshots</id>
		<url>http://oss.sonatype.org/content/repositories/vaadin-snapshots/</url>
		<releases>
			<enabled>false</enabled>
		</releases>
		<snapshots>
			<enabled>true</enabled>
		</snapshots>
	</pluginRepository>
</pluginRepositories>
<dependencies>
	<dependency>
		<groupId>com.vaadin</groupId>
		<artifactId>vaadin-server</artifactId>
		<version>${vaadin.version}</version>
	</dependency>
	<!--
	<dependency>
		<groupId>com.vaadin</groupId>
		<artifactId>vaadin-client-compiled</artifactId>
		<version>${vaadin.version}</version>
	</dependency>
	<dependency>
		<groupId>com.vaadin</groupId>
		<artifactId>vaadin-client</artifactId>
		<version>${vaadin.version}</version>
		<scope>provided</scope>
	</dependency>
	 -->
	<dependency>
		<groupId>com.vaadin</groupId>
		<artifactId>vaadin-themes</artifactId>
		<version>${vaadin.version}</version>
	</dependency>
	<dependency>
		<groupId>javax.servlet</groupId>
		<artifactId>servlet-api</artifactId>
		<version>2.4</version>
		<scope>provided</scope>
	</dependency>
</dependencies>

<build>
	<plugins>
		<plugin>
			<groupId>org.apache.maven.plugins</groupId>
			<artifactId>maven-compiler-plugin</artifactId>
			<configuration>
				<source>1.6</source>
				<target>1.6</target>
			</configuration>
		</plugin>
		<!-- As we are doing "inplace" GWT compilation, ensure the widgetset -->
		<!-- directory is cleaned properly -->
		<plugin>
			<artifactId>maven-clean-plugin</artifactId>
			<version>2.4.1</version>
			<configuration>
				<filesets>
					<fileset>
						<directory>src/main/webapp/VAADIN/widgetsets</directory>
					</fileset>
				</filesets>
			</configuration>
		</plugin>
		<plugin>
			<groupId>com.vaadin</groupId>
			<artifactId>vaadin-maven-plugin</artifactId>
			<version>${vaadin.plugin.version}</version>
			<configuration>
				<extraJvmArgs>-Xmx512M -Xss1024k</extraJvmArgs>
				<!-- <runTarget>mobilemail</runTarget> -->
				<!-- We are doing "inplace" but into subdir VAADIN/widgetsets. This
					way compatible with Vaadin eclipse plugin. -->
				<webappDirectory>${basedir}/src/main/webapp/VAADIN/widgetsets</webappDirectory>
				<modules>
					<module>com.test.config.prop.AppWidgetSet</module>
				</modules>
				<hostedWebapp>${basedir}/src/main/webapp/VAADIN/widgetsets</hostedWebapp>
				<noServer>true</noServer>
				<!-- Remove draftCompile when project is ready -->
				<draftCompile>true</draftCompile>
				<compileReport>true</compileReport>
				<style>DETAILED</style>
				<strict>true</strict>
				<runTarget>http://localhost:8080/</runTarget>
			</configuration>
			<executions>
				<execution>
					<configuration>
						<!-- if you don't specify any modules, the plugin will find them -->
						<!-- <modules> <module>com.vaadin.demo.mobilemail.gwt.ColorPickerWidgetSet</module>
							</modules> -->
					</configuration>
					<goals>
						<goal>resources</goal>
						<goal>update-widgetset</goal>
						<goal>compile</goal>
					</goals>
				</execution>
			</executions>
		</plugin>
		<plugin>
			<groupId>org.mortbay.jetty</groupId>
			<artifactId>jetty-maven-plugin</artifactId>
		</plugin>
	</plugins>
	<pluginManagement>
		<plugins>
			<!--This plugin's configuration is used to store Eclipse m2e settings
				only. It has no influence on the Maven build itself. -->
			<plugin>
				<groupId>org.eclipse.m2e</groupId>
				<artifactId>lifecycle-mapping</artifactId>
				<version>1.0.0</version>
				<configuration>
					<lifecycleMappingMetadata>
						<pluginExecutions>
							<pluginExecution>
								<pluginExecutionFilter>
									<groupId>com.vaadin</groupId>
									<artifactId>
										vaadin-maven-plugin
									</artifactId>
									<versionRange>
										[7.0.1,)
									</versionRange>
									<goals>
										<goal>resources</goal>
										<goal>update-widgetset</goal>
										<goal>compile</goal>
									</goals>
								</pluginExecutionFilter>
								<action>
									<ignore></ignore>
								</action>
							</pluginExecution>
						</pluginExecutions>
					</lifecycleMappingMetadata>
				</configuration>
			</plugin>
		</plugins>
	</pluginManagement>
</build>

I get this error when I update the Vaadin version and compile the widgetset but forget to recompile the theme. It doesn’t look like you are compiling your theme, but I haven’t done enough w/ the maven archetypes to know if it will invoke the theme compile or not.

You could try manually compiling your theme before deploying to see if that helps…

I didn’t check the POM, but I suppose it doesn’t have a wrong version of the themes JAR.

Another possibility would be the theme of the old version being cached too aggressively - e.g. Chrome tends to do that, disregarding what the server has told it about caching. To check for this, clear the browser cache or do a few forced full reloads (Ctrl-F5 or Shift-F5). Also the server might cache themes.

I always use ctrl+f5 in all browsers and result was the same.

It seems it is only happening when using scss theme.

As i have the productionMode = false in web.xml i am not explicit compiling the theme, the Sass servlet would compile the theme automatically right?

This issue is easy to reproduce also with Vaadin Plug-in for Eclipse. I wrote
a ticket
about it.