From 0b7457325200162961cae52e7d871db928dc3cd9 Mon Sep 17 00:00:00 2001 From: Zhe Sun <31067185+ZheSun88@users.noreply.github.com> Date: Thu, 23 May 2019 09:43:31 +0300 Subject: Update broken docs syntax in github (#11596) * Add delay to the unstable test * Add delay for unstable tests * Update broken docs syntax in github * Merge branch 'master' into ZheSun88-patch-1 * Update doc reference syntax * Merge branch 'ZheSun88-patch-1' of github.com:vaadin/framework into ZheSun88-patch-1 # Conflicts: # documentation/components/components-overview.asciidoc * Merge branch 'master' into ZheSun88-patch-1 * use .asciidoc * Merge remote-tracking branch 'origin/ZheSun88-patch-1' into ZheSun88-patch-1 * use .asciidoc * Merge branch 'master' into ZheSun88-patch-1 --- documentation/application/application-environment.asciidoc | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) (limited to 'documentation/application/application-environment.asciidoc') diff --git a/documentation/application/application-environment.asciidoc b/documentation/application/application-environment.asciidoc index 51240c59f8..87e1591082 100644 --- a/documentation/application/application-environment.asciidoc +++ b/documentation/application/application-environment.asciidoc @@ -62,7 +62,7 @@ If your application uses a special theme (look and feel), you must include it in Widget sets (OPTIONAL):: If your application uses add-ons or custom widgets, they must be compiled to the [filename]#VAADIN/widgetset/# directory. When using add-ons, this is done automatically in Maven projects. -See <> for more information. +See <<../addons/addons-maven#addons.maven, "Using Add-ons in a Maven Project">> for more information. [[application.environment.webservlet]] == Web Servlet Class @@ -177,7 +177,7 @@ In a project that does not use add-ons or custom widgets, the [classname]#com.va It contains all the widgets for the built-in Vaadin components. When using add-ons, the Vaadin Maven Plugin automatically defines an [classname]#AppWidgetSet# that includes all the add-on widget sets. -The widget set must be compiled, as described in <> (for add-ons) or <> (for custom widgets and client-side modules), and properly deployed with the application. +The widget set must be compiled, as described in <<../addons/addons-overview.asciidoc#addons.overview,"Using Vaadin Add-ons">> (for add-ons) or <<../clientside/clientside-compiling#clientside.compiling,"Compiling a Client-Side Module">> (for custom widgets and client-side modules), and properly deployed with the application. [[application.environment.servlet-mapping]] == Servlet Mapping with URL Patterns @@ -262,7 +262,7 @@ features. For production use, you should have the [classname]#@VaadinServletConfiguration#. The parameter and the debug and production modes are described in more detail in -<>. @@ -282,7 +282,7 @@ defined in the context as well. === UI Heartbeat Vaadin monitors UIs by using a heartbeat, as explained in -<>. If the user closes the browser window of a Vaadin application or navigates to another page, the Client-Side Engine running in the page stops sending heartbeat to the server, and the server eventually cleans up the @@ -330,7 +330,7 @@ request. === Push Mode You can enable server push, as described in -<>, +<<../advanced/advanced-push#advanced.push,"Server Push">>, for a UI either with a [classname]#@Push# annotation for the UI or in the descriptor. The push mode is defined with a [parameter]#pushmode# init parameter. The [literal]#++automatic++# mode pushes changes to the browser automatically after -- cgit v1.2.3