QML ValueSpacePublisher always starts valuespace server, leading to asserts

Using master (and possibly older versions too), you can easily make pub/sub assert with the following setup:

1) create a c++/qml project
2) call QValueSpace::initValueSpaceServer(); in c++ code
3) create one ValueSpacePublisher

QML element in your qml code

The code will assert because the QDeclarativeValueSpacePublisher element will force-start the server, but it's already running, so the program will assert to qvaluespacemanager.cpp:66.

I could also imagine that if you have more than one QML publisher element in a pure qml application, the same assert would still occur.