diff options
author | DiegoSanzVi <40760222+DiegoSanzVi@users.noreply.github.com> | 2018-12-17 13:24:50 +0200 |
---|---|---|
committer | Sun Zhe <31067185+ZheSun88@users.noreply.github.com> | 2018-12-17 13:24:50 +0200 |
commit | ccb1c45a6a85e1fe6d0497d8b9bafc130a01ca92 (patch) | |
tree | d168ab4eb121c96942be3dbb021140831bd1e678 /documentation | |
parent | 9158f727fe2b80ec47eae91bcc2a2837346a7aad (diff) | |
download | vaadin-framework-ccb1c45a6a85e1fe6d0497d8b9bafc130a01ca92.tar.gz vaadin-framework-ccb1c45a6a85e1fe6d0497d8b9bafc130a01ca92.zip |
Error advanced-osgi formating (#11382)
Some snippets codes do not render properly.
Diffstat (limited to 'documentation')
-rw-r--r-- | documentation/advanced/advanced-osgi.asciidoc | 5 |
1 files changed, 5 insertions, 0 deletions
diff --git a/documentation/advanced/advanced-osgi.asciidoc b/documentation/advanced/advanced-osgi.asciidoc index 0cb7a57539..8d8a99990f 100644 --- a/documentation/advanced/advanced-osgi.asciidoc +++ b/documentation/advanced/advanced-osgi.asciidoc @@ -21,11 +21,13 @@ Vaadin application for OSGi should be a valid bundle, i.e. it should be packaged The easiest way to convert regular maven-based Vaadin application into a valid OSGi bundle consists of five steps: * Change packaging type to `jar` in your `pom.xml`: + [source, xml] ---- <packaging>jar</packaging> ---- * Change the scope for all vaadin dependencies from default to `provided`, like this: + [source, xml] ---- <dependency> @@ -35,6 +37,7 @@ The easiest way to convert regular maven-based Vaadin application into a valid O </dependency> ---- * Add OSGi-related dependencies to the project + [source, xml] ---- <groupId>com.vaadin</groupId> @@ -62,6 +65,7 @@ The easiest way to convert regular maven-based Vaadin application into a valid O </dependency> ---- * Setup necessary plugins for building the project: + [source, xml] ---- <build> @@ -93,6 +97,7 @@ The easiest way to convert regular maven-based Vaadin application into a valid O </build> ---- * Add bundle script (`bnd.bnd`) into the project root folder: + [source, text] ---- Bundle-Name: ${project.name} |