From a0e0596ee781b62f95472f7a4e84ece174832bb0 Mon Sep 17 00:00:00 2001
From: Wouter Born <github@maindrain.net>
Date: Sun, 24 May 2020 18:44:59 +0200
Subject: [PATCH] Fix broken ESH links

Signed-off-by: Wouter Born <github@maindrain.net>
---
 configuration/items.md                  | 2 +-
 configuration/multimedia.md             | 8 ++++----
 configuration/rules-dsl.md              | 2 +-
 developers/legacy/compatibilitylayer.md | 2 +-
 4 files changed, 7 insertions(+), 7 deletions(-)

diff --git a/configuration/items.md b/configuration/items.md
index 086e49c4d8..f5bb199f67 100644
--- a/configuration/items.md
+++ b/configuration/items.md
@@ -119,7 +119,7 @@ More details about all of the available Item types and their commands are availa
 [Item Types Overview]({{base}}/concepts/items.html)
 
 To learn about the technical internals of the individual Item types, please refer to:
-[Javadoc on Generic Item and its subclasses](https://eclipse.org/smarthome/documentation/javadoc/org/eclipse/smarthome/core/items/GenericItem.html)
+[Javadoc on Generic Item and its subclasses](https://www.openhab.org/javadoc/v2.5/org/openhab/core/items/genericitem)
 
 <!-- TODO: Random content. Doesn't make sense here. Might be changed to be a more general example for diverse Items
 
diff --git a/configuration/multimedia.md b/configuration/multimedia.md
index 66b702d9ff..deb84a1990 100644
--- a/configuration/multimedia.md
+++ b/configuration/multimedia.md
@@ -9,7 +9,7 @@ title: Multimedia
 
 ## Volume
 
-The framework supports some base [functions](https://www.eclipse.org/smarthome/documentation/javadoc/org/eclipse/smarthome/model/script/actions/Audio.html#getMasterVolume--) to control the audio sinks' volume.
+The framework supports some base [functions](https://www.openhab.org/javadoc/v2.5/org/eclipse/smarthome/model/script/actions/audio#method.summary) to control the audio sinks' volume.
 
 ### Actions
 
@@ -58,7 +58,7 @@ openhab> smarthome:audio stream example.com
 
 ### Actions
 
-Alternatively the [`playSound()`](https://www.eclipse.org/smarthome/documentation/javadoc/org/eclipse/smarthome/model/script/actions/Audio.html#playSound-java.lang.String-) or [`playStream()`](https://www.eclipse.org/smarthome/documentation/javadoc/org/eclipse/smarthome/model/script/actions/Audio.html#playStream-java.lang.String-) functions can be used in DSL rules:
+Alternatively the [`playSound()`](https://www.openhab.org/javadoc/v2.5/org/eclipse/smarthome/model/script/actions/audio#playSound(java.lang.String)) or [`playStream()`](https://www.openhab.org/javadoc/v2.5/org/eclipse/smarthome/model/script/actions/audio#playStream(java.lang.String)) functions can be used in DSL rules:
 
 - `playSound(String filename)` :	plays a sound from the sounds folder to the default sink
 - `playSound(String filename, PercentType volume)` :	plays a sound with the given volume from the sounds folder to the default sink
@@ -109,7 +109,7 @@ openhab> smarthome:voice say Hello world!
 
 ### Actions
 
-Alternatively you can execute such commands within DSL rules by using the [`say()`](https://www.eclipse.org/smarthome/documentation/javadoc/org/eclipse/smarthome/core/voice/VoiceManager.html#say-java.lang.String-) function:
+Alternatively you can execute such commands within DSL rules by using the [`say()`](https://www.openhab.org/javadoc/v2.5/org/eclipse/smarthome/core/voice/voicemanager#say(java.lang.String)) function:
 
 ```java
 say("Hello world!")
@@ -151,7 +151,7 @@ openhab> smarthome:voice interpret turn on the light
 The default human language interpreter will be used.
 In case of interpretation error, the error message will be said using the default voice and default audio sink.
 
-Again, such a command can also be entered within DSL rules (using the [`interpret()`](https://www.eclipse.org/smarthome/documentation/javadoc/org/eclipse/smarthome/core/voice/VoiceManager.html#interpret-java.lang.String-) function)
+Again, such a command can also be entered within DSL rules (using the [`interpret()`](https://www.openhab.org/javadoc/v2.5/org/eclipse/smarthome/core/voice/voicemanager#interpret(java.lang.String)) function)
 
 ```java
 interpret("turn on the light")
diff --git a/configuration/rules-dsl.md b/configuration/rules-dsl.md
index 28dac8bd90..dd22c0e224 100644
--- a/configuration/rules-dsl.md
+++ b/configuration/rules-dsl.md
@@ -380,7 +380,7 @@ There are two ways to discover these methods:
 
 - Use the [openHAB VS Code Extension](/docs/configuration/editors.html#editors.html#openhab-vs-code-extension) and the `<ctrl><space>` key combo to list all the available methods
 - Look at the JavaDocs for the given type.
-For example, the [JavaDoc for HSBType](http://www.eclipse.org/smarthome/documentation/javadoc/index.html?org/eclipse/smarthome/core/library/types/HSBType.html) shows getRed, getBlue, and getGreen methods.
+For example, the [JavaDoc for HSBType](https://www.openhab.org/javadoc/v2.5/org/eclipse/smarthome/core/library/types/hsbtype) shows getRed, getBlue, and getGreen methods.
 These methods can be called in Rules-DSL without the "get" part in name as in `(MyColorItem.state as HSBType).red)`.
 They retrieve the state of MyColorItem and then casts it as HSBType to be able to use the methods associated with the HSBType.
 
diff --git a/developers/legacy/compatibilitylayer.md b/developers/legacy/compatibilitylayer.md
index 6c319181a5..e8640691cc 100644
--- a/developers/legacy/compatibilitylayer.md
+++ b/developers/legacy/compatibilitylayer.md
@@ -38,4 +38,4 @@ Here is what you need to do:
 This config file then needs to be added to `features/openhab-addons-external/pom.xml` so that the build is aware of it.
 The feature itself is then added to `features/openhab-addons/src/main/feature/feature.xml`, referencing the bundle, the config file, and its dependencies (if any). The result should look [similar to this](https://github.com/openhab/openhab/pull/3988/files).
 This will automatically make the add-on a part of the distro with the next build.
-1. Note that with defining a Karaf feature, bindings are available for installation through the Paper UI in the "Extensions" menu, but they are not listed under "Configuration->Bindings" (although it is fully operational after installation). In order to have bindings listed there as well, you need to add some meta-information to the binding bundle. This information should be put into `ESH-INF/binding/binding.xml` and its content is [described here](https://www.eclipse.org/smarthome/documentation/development/bindings/xml-reference.html#xml-structure-for-binding-definitions). Do not forget to add `ESH-INF` to your `build.properties`, so that it is packaged in the bundle. See a [real life example of such meta-data here](https://github.com/openhab/openhab/blob/master/bundles/binding/org.openhab.binding.nest/ESH-INF/binding/binding.xml) - note the `service-id` element in the XML, which needs to point to the service id of your binding, which is by default `org.openhab.<bindingId>` for all 1.x bindings.
+1. Note that with defining a Karaf feature, bindings are available for installation through the Paper UI in the "Extensions" menu, but they are not listed under "Configuration->Bindings" (although it is fully operational after installation). In order to have bindings listed there as well, you need to add some meta-information to the binding bundle. This information should be put into `ESH-INF/binding/binding.xml` and its content is [described here](/docs/developer/bindings/binding-xml.html#xml-structure-for-binding-definitions). Do not forget to add `ESH-INF` to your `build.properties`, so that it is packaged in the bundle. See a [real life example of such meta-data here](https://github.com/openhab/openhab/blob/master/bundles/binding/org.openhab.binding.nest/ESH-INF/binding/binding.xml) - note the `service-id` element in the XML, which needs to point to the service id of your binding, which is by default `org.openhab.<bindingId>` for all 1.x bindings.