BoV: Updated library list in Getting Started to Vaadin 8.

Change-Id: I96401a60e2e06bff02d89f5b8cd83aa293a948fc

4 files changed, 11 insertions, 17 deletions

diff --git a/documentation/getting-started/getting-started-first-project.asciidoc b/documentation/getting-started/getting-started-first-project.asciidoc
index bfc9ddf154..ede6f77841 100644
--- a/documentation/getting-started/getting-started-first-project.asciidoc
+++ b/documentation/getting-started/getting-started-first-project.asciidoc
@@ -485,7 +485,7 @@ version.
 +
 [subs="normal"]
 ----
-<!ENTITY vaadin.version "**7.x.x**">
+<!ENTITY vaadin.version "**8.x.x**">
 ----
 +
 You can specify either a fixed version number, as shown in the above example, or
diff --git a/documentation/getting-started/getting-started-libraries.asciidoc b/documentation/getting-started/getting-started-libraries.asciidoc
index 785444b5ea..3ff27b8acb 100644
--- a/documentation/getting-started/getting-started-libraries.asciidoc
+++ b/documentation/getting-started/getting-started-libraries.asciidoc
@@ -11,23 +11,23 @@ Vaadin comes as a set of library JARs, of which some are optional or alternative
 ones, depending on whether you are developing server-side or client-side
 applications, whether you use add-on components, or use CSS or Sass themes.
 
-[filename]#vaadin-server-7.x.x.jar#::
+[filename]#vaadin-server-8.x.x.jar#::
 The main library for developing server-side Vaadin applications, as described in
 <<dummy/../../../framework/application/application-overview.asciidoc#application.overview,"Writing a Server-Side Web Application">>.
 It requires the [filename]#vaadin-shared# and the [filename]#vaadin-themes# libraries.
 You can use the pre-built [filename]#vaadin-client-compiled# for server-side development, unless you need add-on components or custom widgets.
 
-[filename]#vaadin-shared-7.x.x.jar#::
+[filename]#vaadin-shared-8.x.x.jar#::
 A shared library for server-side and client-side development.
 It is always needed.
 
-[filename]#vaadin-client-7.x.x.jar#::
+[filename]#vaadin-client-8.x.x.jar#::
 The client-side Vaadin framework, including the basic GWT API and Vaadin-specific widgets and other additions.
 It is required when using the [filename]#vaadin-client-compiler# to compile client-side modules.
 It is not needed if you just use the server-side framework with the pre-compiled Client-Side Engine.
 You should not deploy it with a web application.
 
-[filename]#vaadin-client-compiler-7.x.x.jar#::
+[filename]#vaadin-client-compiler-8.x.x.jar#::
 The Vaadin Client Compiler is a Java-to-JavaScript compiler that allows building client-side modules, such as the Client-Side Engine (widget set) required for server-side applications.
 The compiler is needed, for example, for compiling add-on components to the application widget set, as described in <<dummy/../../../framework/addons/addons-overview.asciidoc#addons.overview,"Using Vaadin Add-ons">>.
 +
@@ -36,20 +36,14 @@ For detailed information regarding the compiler, see
 <<dummy/../../../framework/clientside/clientside-compiling#clientside.compiling,"Compiling a Client-Side Module">>.
 Note that you should not deploy this library with a web application.
 
-[filename]#vaadin-client-compiled-7.x.x.jar#::
+[filename]#vaadin-client-compiled-8.x.x.jar#::
 A pre-compiled Vaadin Client-Side Engine (widget set) that includes all the basic built-in widgets in Vaadin.
 This library is not needed if you compile the application widget set with the Vaadin Client Compiler.
 
-[filename]#vaadin-themes-7.x.x.jar#::
+[filename]#vaadin-themes-8.x.x.jar#::
 Vaadin built-in themes both as SCSS source files and precompiled CSS files.
 The library is required both for basic use with CSS themes and for compiling custom Sass themes.
 
-[filename]#vaadin-sass-compiler-1.x.x.jar#::
-The Vaadin Sass Compiler compiles Sass themes to CSS, as described in <<dummy/../../../framework/themes/themes-sass#themes.sass,"Syntactically Awesome
-Stylesheets (Sass)">>.
-It requires the [filename]#vaadin-themes-7.x.x.jar# library, which contains the Sass sources for the built-in themes.
-The library needs to be included in deployment in development mode to allow on-the-fly compilation of themes, but it is not needed in production deployment, when the themes are compiled before deployment.
-
 Some of the libraries depend on each other as well as on the dependency libraries provided in the [filename]#lib# folder of the installation package, especially the [filename]#lib/vaadin-shared-deps.jar#.
 
 The different ways to install the libraries are described in the subsequent sections.
diff --git a/documentation/getting-started/getting-started-maven.asciidoc b/documentation/getting-started/getting-started-maven.asciidoc
index 501f072912..aca26b8115 100644
--- a/documentation/getting-started/getting-started-maven.asciidoc
+++ b/documentation/getting-started/getting-started-maven.asciidoc
@@ -34,7 +34,7 @@ line):
 [prompt]#$# [command]#mvn# archetype:generate \
    -DarchetypeGroupId=com.vaadin \
    -DarchetypeArtifactId=[replaceable]#vaadin-archetype-application# \
-   -DarchetypeVersion=[replaceable]#7.x.x# \
+   -DarchetypeVersion=[replaceable]#8.x.x# \
    -DgroupId=[replaceable]#com.pany# \
    -DartifactId=[replaceable]#project-name# \
    -Dversion=[replaceable]#0.1# \
diff --git a/documentation/themes/themes-creating.asciidoc b/documentation/themes/themes-creating.asciidoc
index a28812b36d..339778910e 100644
--- a/documentation/themes/themes-creating.asciidoc
+++ b/documentation/themes/themes-creating.asciidoc
@@ -234,15 +234,15 @@ projects).
 ----
 [subs="normal"]
 ----
-[prompt]#$# [command]#unzip# path-to/vaadin-server-7.x.x.jar 'VAADIN/*'
+[prompt]#$# [command]#unzip# path-to/vaadin-server-8.x.x.jar 'VAADIN/*'
 ----
 [subs="normal"]
 ----
-[prompt]#$# [command]#unzip# path-to/vaadin-themes-7.x.x.jar 'VAADIN/*'
+[prompt]#$# [command]#unzip# path-to/vaadin-themes-8.x.x.jar 'VAADIN/*'
 ----
 [subs="normal"]
 ----
-[prompt]#$# [command]#unzip# path-to/vaadin-client-compiled-7.x.x.jar 'VAADIN/*'
+[prompt]#$# [command]#unzip# path-to/vaadin-client-compiled-8.x.x.jar 'VAADIN/*'
 ----
 You can also serve static content from a front-end caching server, which reduces
 the load of the application server. In portals, you install the themes globally