according to https://bugs.eclipse.org/bugs/show_bug.cgi?id=544977#c21 the
scenario of using the ManifestBuilder without setting the PluginNature is
not a supported scenario. Besides, it doesn't help to get rid of the new
Eclipse warning regarding non-exported packages.
This reverts commit 063484e29f.
this way, no patching of the userGroupProvider property after
de-serialization is necessary, and no replacement of a User object in
the UserStore should ever happen.
Change-Id: I23a8ae53b6a53ca89a2a0b8a11dc779f4034db57
With this, the "available" attribute of the response document already is
a good indicator of the instance's availability. The next thing will be
to map this to a 5xx resonse code if the instance is not yet available
Change-Id: I87a179b04a811843bbd8cf85bba58c1eed81d46c
always pass operations to be sent to master into the queue so they
cannot be delivered to the master earlier than other queued operations
after connectivity has been restored
Change-Id: I7b1409dc4663659039058ce2c0511a26009114b4
Axel Uhl
Steffen Schaefer