You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

getting-started-libraries.asciidoc 3.5KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758
  1. ---
  2. title: Vaadin Libraries
  3. order: 20
  4. layout: page
  5. ---
  6. [[getting-started.libraries]]
  7. = Vaadin Libraries
  8. Vaadin Framework comes as a set of library JARs, of which some are optional or alternative
  9. ones, depending on whether you are developing server-side or client-side
  10. applications, whether you use add-on components, or use CSS or Sass themes.
  11. [filename]#vaadin-server-8.x.x.jar#::
  12. The main library for developing server-side Vaadin applications, as described in
  13. <<../application/application-overview.asciidoc#application.overview,"Writing a Server-Side Web Application">>.
  14. It requires the [filename]#vaadin-shared# and the [filename]#vaadin-themes# libraries.
  15. You can use the pre-built [filename]#vaadin-client-compiled# for server-side development, unless you need add-on components or custom widgets.
  16. [filename]#vaadin-themes-8.x.x.jar#::
  17. Vaadin Framework built-in themes both as SCSS source files and precompiled CSS files.
  18. The library is required both for basic use with CSS themes and for compiling custom Sass themes.
  19. [filename]#vaadin-push-8.x.x.jar#::
  20. The implementation of server push for Vaadin Framework.
  21. This is needed for web applications which use server push (e.g. using the @Push annotation in a Servlet class).
  22. [filename]#vaadin-shared-8.x.x.jar#::
  23. A shared library for server-side and client-side development.
  24. It is always needed.
  25. [filename]#vaadin-client-compiled-8.x.x.jar#::
  26. A pre-compiled Vaadin Client-Side Engine (widget set) that includes all the basic built-in widgets in Vaadin.
  27. This library is not needed if you compile the application widget set with the Vaadin Client Compiler.
  28. [filename]#vaadin-client-8.x.x.jar#::
  29. The client-side Vaadin Framework, including the basic GWT API and Vaadin-specific widgets and other additions.
  30. It is required when using the [filename]#vaadin-client-compiler# to compile client-side modules.
  31. It is not needed if you just use the server-side framework with the pre-compiled Client-Side Engine.
  32. You should not deploy it with a web application.
  33. [filename]#vaadin-client-compiler-8.x.x.jar#::
  34. 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.
  35. The compiler is needed, for example, for compiling add-on components to the application widget set, as described in <<../addons/addons-overview.asciidoc#addons.overview,"Using Vaadin Add-ons">>.
  36. +
  37. For detailed information regarding the compiler, see
  38. <<../clientside/clientside-compiling#clientside.compiling,"Compiling a Client-Side Module">>.
  39. Note that you should not deploy this library with a web application.
  40. [filename]#vaadin-compatibility-*-8.x.x.jar#::
  41. The Vaadin Framework 7 compatibility packages contain the components and themes that are present in framework version 7, but not in version 8. These packages exist for making it easier to migrate from version 7 to 8. There is a compatibility package for everything except [filename]#vaadin-client-compiler#.
  42. Some of the libraries depend on each other, for instance [filename]#vaadin-shared# is included as a dependency of [filename]#vaadin-server#.
  43. The different ways to install the libraries are described in the subsequent sections.
  44. Note that the [filename]#vaadin-client-compiler# and [filename]#vaadin-client# JARs should not be deployed with the web application. The Maven scope [filename]#provided# can be used.
  45. Some other libraries, such as [filename]#vaadin-sass-compiler#, are not needed in production deployment.