Gerko,
Did you encounter a situation where your deployed application seemed to bundle both the 7.5.10 and 7.6.0 libraries?
- John
Gerko,
Did you encounter a situation where your deployed application seemed to bundle both the 7.5.10 and 7.6.0 libraries?
John,
The default ivy libs were 7.6.0, but the widgetset-compile and the ivy nodeploy jars were 7.5.9.
Gerko
Gerko,
The multi-module maven project has been cleaned. The libraries all appear to be 7.6.0.
Here are the vaadin-specific libraries. Does anyone spot a conflict?
[INFO]
--- maven-dependency-plugin:2.8:list (default-cli) @ venn-frontend-vaadin-poc ---
[INFO]
com.vaadin:vaadin-testbench-api:jar:7.4.8:test
[INFO]
com.vaadin:vaadin-client-compiler-deps:jar:1.2.0:provided
[INFO]
com.vaadin:vaadin-testbench-core:jar:4.0.3:test
[INFO]
com.vaadin:vaadin-push:jar:7.6.0:compile
[INFO]
com.vaadin.external.atmosphere:atmosphere-runtime:jar:2.2.7.vaadin1:compile
[INFO]
com.vaadin:vaadin-server:jar:7.6.0:compile
[INFO]
com.vaadin:vaadin-themes:jar:7.6.0:compile
[INFO]
com.vaadin:vaadin-sass-compiler:jar:0.9.13:compile
[INFO]
com.vaadin:vaadin-client-compiler:jar:7.6.0:provided
[INFO]
com.vaadin:vaadin-client:jar:7.6.0:provided
[INFO]
com.vaadin.external.flute:flute:jar:1.3.0.gg2:compile
[INFO]
com.vaadin:vaadin-testbench:jar:4.0.3:test
[INFO]
com.vaadin.addon:vaadin-charts:jar:2.1.3:compile
[INFO]
com.vaadin.external.streamhtmlparser:streamhtmlparser-jsilver:jar:0.0.10.vaadin1:compile
[INFO]
org.vaadin.addon:confirmdialog:jar:2.1.3:compile
[INFO]
com.vaadin.external.google:guava:jar:16.0.1.vaadin1:compile
[INFO]
com.vaadin.external.slf4j:vaadin-slf4j-jdk14:jar:1.6.1:compile
[INFO]
com.vaadin:vaadin-shared:jar:7.6.0:compile
Thanks in advance,
Check what the info tab in the ?debug window says, that will tell you what is really in use
Shows 7.5.8?
As I suspected, you need to fix that Recompile your widget set using 7.6.0
Hmmm…even after running the following maven goals (see below) - still showing 7.5.8 in ?debug:
Try
mvn vaadin:compile -Dgwt.compiler.force=true
Otherwise, remove the widget set first (mvn clean vaadin:clean) and ensure the app does not start. Then run vaadin:compile again
Hello Artur,
I have attempted the recommended operations but still see "
Client engine version 7.5.8
" in the debug window.
mvn clean
mvn clean vaadin:clean vaadin:compile
mvn clean vaadin:clean vaadin:compile -Dgwt.compiler.force=true
Any suggestions?
Even after manually clearing Widgetset directories can see “var $gwt_version = "7.5.8"” in:
53CD41F41F6D8C3C83FB4A808EFD8C1A.cache.js
com.jgk.venn.frontend.vaadin.poc.PocWidgetSet.devmode.js
How is the $gwt_version set?
\
ok 7.6.0 up and running on the client
John,
What was the magic incantation to finally get the client to show 7.6.0?
Thanks!
EDIT:
mvn vaadin:compile -Dgwt.compiler.force=true
worked for me the first time.
Andrew,
For some reason when compiling the widget set (vaadin:compile) the old version [7.5.8]
was sticking.
I went into each module (a multi-module maven project) and manually removed the widgetset directory and then rebuilt the widgetset.