Using the DESY identifier here was done by mistake when introducing the SPDX headers.

Co-authored-by: Martin Hierholzer <martin.hierholzer@desy.de>

* Use templated version to add a trigger.

A trigger is needed for Poll type inputs. Still it can not be used for
Devices. Here one has to call addSource manually.

* No need to use a trigger. Fix connections by moving all to history.

Trigger is only needed for DeviceModules. So in case of device addSource
still needs to be used, because no tags are present for devices.

* Add option to specify the directory where history will appear in CS.

* Remove CS tag not needed any more.

* Update documentation.

* Update documentation of logging module.

* Remove CS tag not needed any more.

* Remove parameter not needed. AddSource for ConnectingDeviceModule. Docu.

* Create test case for testing multiple modules having the same.

* Use message IDs to support modules with similar names.

ToDo: Remove variable connections to CS like with MicroDAQ.

* Use automatic connection via CS. Rebuild hierarchy in Logging module.

* Put logging variables into a separate hierarchy level.

* Let user write to alias via CS. Keep last message in the PV.

Before the message was always cleared after writing it. Now a new log
level is used to indicate the situation that write was called on the
message PV without calling sendMessage - it happens if the owning module
calls writeAll(). Now the last message of each sender is availble in the
CS.

* Add test with modified hierarchy.

* Clang formaat applied.

* Hide internal PVs. Use different internal tag to work with regex.

Introduce StatusWithMessage and StatusWithMessageReader which handle this.
It is used in DeviceModule error reporting.
This is a preparation in order that we can report errors consistently to DOOCS, in DoocsAdapter

make StatusAggregator use StatusWithMessage

it should output always status code + string
on the input side, connects to either status or status + string
corresponding string input is found automatically
NOTE: DeviceModule API change, the status output variables are
renamed from (status, message) to (status, status_message)!

update testing of DeviceModule outputs

because of API change of DeviceModule  (renamed message ->
status_message)

fix crash and improve message and test

- fix crash due to incorrect handling of cast to Derived
- improve message output
- make existing tests pass
- add test for status message of StatusAggregator

move StatusWithMessageReaderBase and Status def to ControlSystemAdapter

since it is required from ApplicationCore as well as from the adapters

it currently fails, showing an existing problem

This fixes redmine issue #8358 (#3 on github)

* spec tests: Data validity propagation
* update documentation links spec <-> tests

Co-authored-by: Dietrich Rothe <dietrich.rothe@desy.de>

Implement systematic tests for exception handling along specification.

This fixes redmin issues #8374, #8520 and #8364.

- testCircularDependencyFaultyFlags now uses modern AC without defining CS module and overriding defineConnections()

# Please enter the commit message for your changes. Lines starting
# with '#' will be ignored, and an empty message aborts the commit.
#
# On branch master
# Your branch is up to date with 'origin/master'.
#
# Changes to be committed:
#	modified:   include/DeviceModule.h
#	modified:   src/DeviceModule.cc
#	modified:   tests/executables_src/testCircularDependencyFaultyFlags.cc
#
# Untracked files:
#	build-example-Desktop-Debug/
#	build-example2-Desktop-Debug/
#	build-example_status_monitor-Desktop-Debug/
#	demoBidirectionalVariables/
#	example2b/
#	include/ApplicationModule_BACKUP_1938963.h
#	include/ApplicationModule_BASE_1938963.h
#	include/ApplicationModule_LOCAL_1938963.h
#	include/ApplicationModule_REMOTE_1938963.h
#	message.txt
#	tests/testVirtualHierarchy.xlmap
#

The new order has the following advantages:
- values 0=OK and 1=Fault are compatible with frequent use of booleans like "is_error"
- values are matching ("accidentally") the DOOCS convention

Circular dependency detection: Outputs which are pogrammatically set to faulty are treated like external inputs.

After discussion with Martin K. we concluded that this monitor makes no sense. Legit cases should use the ExactMonitor
instead (if e.g. a boolean on/off configuration switch is to be observed). The monitoring of a Status value makes
no sense, since we would then have a monitor monitoring another monitor. In that case, the behaviour of the other
monitor should either be corrected, or the monitors should be aggregated with the right aggregator mode.