security alert/cannot upgrade to 7.7.9

General
1

Similar to
https://vaadin.com/forum#!/thread/15647544/15654483
 but a different error.

We were on 7.4.3 and need to upgrade to 7.7.9. When I try to build I get this:

[font=courier new]
hostname}> mvn clean install
[INFO]
Scanning for projects…
[INFO]

[INFO]

[INFO]
Building PPCDConsole Java EE 6 Webapp 2.2-SNAPSHOT
[INFO]

[INFO]

[INFO]
— maven-clean-plugin:2.4.1:clean (default-clean) @ PCSConsole —
[INFO]

[INFO]
— vaadin-maven-plugin:7.7.9:clean (default) @ PCSConsole —
[INFO]
auto discovered modules [com.enterprisedb.pcs.widgetset.PCSAppWidgetSet]

[INFO]

[INFO]
— vaadin-maven-plugin:7.7.9:update-theme (default) @ PCSConsole —
[INFO]
Updating theme VAADIN/themes/pcsconsole
[ERROR]
Error: Could not find or load main class com.vaadin.server.themeutils.SASSAddonImportFileCreator
[ERROR]
Updating theme “VAADIN/themes/pcsconsole” failed
org.codehaus.mojo.gwt.shell.JavaCommandException: Command [[
/bin/sh -c ‘/Library/Java/JavaVirtualMachines/jdk1.7.0_75.jdk/Contents/Home/jre/bin/java’ ‘-Xmx512M’ ‘-Xss1024k’ ‘-classpath’ ]
] failed with status 1
at org.codehaus.mojo.gwt.shell.JavaCommand.execute(JavaCommand.java:327)
at com.vaadin.integration.maven.UpdateThemeMojo.processTheme(UpdateThemeMojo.java:45)
at com.vaadin.integration.maven.AbstractThemeMojo.doExecute(AbstractThemeMojo.java:43)
at org.codehaus.mojo.gwt.shell.AbstractGwtShellMojo.execute(AbstractGwtShellMojo.java:182)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:862)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:286)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:197)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
[INFO]

[INFO]
BUILD FAILURE
[INFO]

[INFO]
Total time: 2.691 s
[INFO]
Finished at: 2017-05-22T09:12:11-04:00
[INFO]
Final Memory: 16M/245M
[INFO]

[/font]

Can someone help me resolve this? Is it a known issue in 7.7.9 that is just now being found after the security email?

Thanks,
Bobby

2

That class surely should exists. I think you have something wrong in your setup.

It may be that old Vaadin files has not been properly cleaned, so you could try to clean the cache manually as follows

cd .m2\repository\com
rm -rf vaadin

Maven we download the new artifacts

SASS compiler has been updated since your last version.

3

Thanks – must have been some stale files. After removing everything from my local repo, the build now fails with:

[INFO] --- vaadin-maven-plugin:7.7.9:compile-theme (default) @ PCSConsole --- [INFO] Updating theme VAADIN/themes/pcsconsole [ERROR] <path>/src/main/resources/VAADIN/themes/<folder>/styles.scss could not be read! [ERROR] Compiling theme "VAADIN/themes/<folder>" failed We don’t have a styles.scss file there, but do have a styles.css instead. Is an .scss file now required? It wasn’t in v7.4.3.

Thanks,
Bobby

4

FWIW, in 7.4.3 there is the same error line but the build still works:

[INFO]
 --- vaadin-maven-plugin:7.4.3:compile-theme (default) @ <app_name> ---
[INFO]
 Updating theme VAADIN/themes/<folder>
[ERROR]
 <path>/src/main/webapp/VAADIN/themes/<folder>/styles.scss could not be read!
[INFO]
 Theme "VAADIN/themes/<folder>" compiled
5

What if you just rename your styles.css to styles.scss?

-Olli

6

It wants the file to be here (using “A” instead of actual project name):
src/main/resources/VAADIN/themes/A/styles.scss

…but currently the file we have is here:
src/main/webapp/VAADIN/themes/A/styles.css

I moved/renamed the file, and am past that part, but now hitting compilation errors (“error: package com.google.gwt.thirdparty.guava.common.base does not exist” if you’re curious). Will look into that separately.

7

After figuring out the rest (apparently vaadin 7.7.9 doesn’t include a google ‘guava’ package we were using), this seems to be working just by renaming that file and moving it.

Thanks all.

8

Great to hear!