openhab-core/itests/itest-common.bndrun

-include: itest-include.bndrun

# If we would like to use a storage at all, we will use the "volatile" storage.
-runblacklist.itest-common: \
    bnd.identity;id='org.openhab.core.storage.json'
[itest] Exclude json and mapdb storage by default for itests (#1193) Signed-off-by: Christoph Weitkamp <github@christophweitkamp.de> 2019-11-08 20:04:48 +01:00			`-include: itest-include.bndrun`
use openHAB Core index, simplify itests and demo app (#503) * use openHAB Core index, simplify itests and demo app Signed-off-by: Markus Rathgeb <maggu2810@gmail.com> 2019-02-01 11:02:39 +01:00
[itest] Exclude json and mapdb storage by default for itests (#1193) Signed-off-by: Christoph Weitkamp <github@christophweitkamp.de> 2019-11-08 20:04:48 +01:00			`# If we would like to use a storage at all, we will use the "volatile" storage.`
Fix unexpected behavior while using runblacklist in itests (#1219) If you would like to use the runblacklist bnd instruction in an integration test it will not work as expected. In my current test case it is not used at all. This is caused because an included file overrides this instruction. IMHO it would be better to use the "Merged Instructions" feature and use a postfix in the included file. This way you can use the non postfixed instruction as usual. See: https://bnd.bndtools.org/chapters/820-instructions.html#merged-instructions Signed-off-by: Markus Rathgeb <maggu2810@gmail.com> 2019-11-17 13:44:16 +01:00			`-runblacklist.itest-common: \`
removed unused mapdb storage bundle (#1488) Signed-off-by: Kai Kreuzer <kai@openhab.org> 2020-05-22 09:52:22 +02:00			`bnd.identity;id='org.openhab.core.storage.json'`