diff options
| author | Matti Tahvonen <matti@vaadin.com> | 2018-12-18 09:12:37 +0200 |
|---|---|---|
| committer | Sun Zhe <31067185+ZheSun88@users.noreply.github.com> | 2018-12-18 09:12:37 +0200 |
| commit | 9c9c962549eb04adac87b0cfe26d24b17843fb6a (patch) | |
| tree | f42f5a29c56ded287a9bc4bb1caa665543e88971 /documentation | |
| parent | 12fe44d807404343c24caee5a1fc53ec031449c5 (diff) | |
| download | vaadin-framework-9c9c962549eb04adac87b0cfe26d24b17843fb6a.tar.gz vaadin-framework-9c9c962549eb04adac87b0cfe26d24b17843fb6a.zip | |
Update portal-osgi.asciidoc (#11384)
Updated versions to latest ones as people often just copy past things. Added comment to urge people to use the versions they need. Removed version from archetype to use the latest by default.
Diffstat (limited to 'documentation')
| -rw-r--r-- | documentation/portal/portal-osgi.asciidoc | 18 |
1 files changed, 9 insertions, 9 deletions
diff --git a/documentation/portal/portal-osgi.asciidoc b/documentation/portal/portal-osgi.asciidoc index b809cef32d..dc03798fda 100644 --- a/documentation/portal/portal-osgi.asciidoc +++ b/documentation/portal/portal-osgi.asciidoc @@ -77,20 +77,20 @@ link:https://github.com/elmot/liferay-7-solid-portlet-example/[] == Deployment a Portlet With OSGi (Maven) An OSGi portlet should be packaged as a JAR with a proper OSGi bundle manifest, and deployed to a portal that has its required bundles installed. -The maven archetype `com.vaadin:vaadin-archetype-liferay-portlet:8.1.0` is a good starting point to build an OSGi portlet application. +The maven archetype `com.vaadin:vaadin-archetype-liferay-portlet` is a good starting point to build an OSGi portlet application. The required bundles (and the application as well) can be installed using link:https://dev.liferay.com/develop/tutorials/-/knowledge_base/7-0/blade-cli[blade client]. The latest client binary can be downloaded from the link: link:https://releases.liferay.com/tools/blade-cli/latest/blade.jar[] -Here is an example script for doing that: +Here is an example script for doing that (be sure to check the versions required by your project using *mvn dependency:list* ): [source, shell] ---- -java -jar blade.jar sh start https://repo1.maven.org/maven2/org/jsoup/jsoup/1.11.0/jsoup-1.11.0.jar +java -jar blade.jar sh start https://repo1.maven.org/maven2/org/jsoup/jsoup/1.11.2/jsoup-1.11.2.jar java -jar blade.jar sh start https://repo1.maven.org/maven2/com/vaadin/external/gentyref/1.2.0.vaadin1/gentyref-1.2.0.vaadin1.jar -java -jar blade.jar sh start https://repo1.maven.org/maven2/com/vaadin/vaadin-shared/8.3.2/vaadin-shared-8.3.2.jar -java -jar blade.jar sh start https://repo1.maven.org/maven2/com/vaadin/vaadin-server/8.3.2/vaadin-server-8.3.2.jar -java -jar blade.jar sh start https://repo1.maven.org/maven2/com/vaadin/vaadin-osgi-integration/8.3.2/vaadin-osgi-integration-8.3.2.jar -java -jar blade.jar sh start https://repo1.maven.org/maven2/com/vaadin/vaadin-client-compiled/8.3.2/vaadin-client-compiled-8.3.2.jar -java -jar blade.jar sh start https://repo1.maven.org/maven2/com/vaadin/vaadin-themes/8.3.2/vaadin-themes-8.3.2.jar -java -jar blade.jar sh start https://repo1.maven.org/maven2/com/vaadin/vaadin-liferay-integration/8.3.2/vaadin-liferay-integration-8.3.2.jar +java -jar blade.jar sh start https://repo1.maven.org/maven2/com/vaadin/vaadin-shared/8.6.3/vaadin-shared-8.6.3.jar +java -jar blade.jar sh start https://repo1.maven.org/maven2/com/vaadin/vaadin-server/8.6.3/vaadin-server-8.6.3.jar +java -jar blade.jar sh start https://repo1.maven.org/maven2/com/vaadin/vaadin-osgi-integration/8.6.3/vaadin-osgi-integration-8.6.3.jar +java -jar blade.jar sh start https://repo1.maven.org/maven2/com/vaadin/vaadin-client-compiled/8.6.3/vaadin-client-compiled-8.6.3.jar +java -jar blade.jar sh start https://repo1.maven.org/maven2/com/vaadin/vaadin-themes/8.6.3/vaadin-themes-8.6.3.jar +java -jar blade.jar sh start https://repo1.maven.org/maven2/com/vaadin/vaadin-liferay-integration/8.6.3/vaadin-liferay-integration-8.6.3.jar java -jar blade.jar sh start file:<path_to_liferay_portlet.jar> ---- |