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.
a CreateSessionServlet has been added to the /sailingserver/test-support
context which is only available during Selenium testing, together with
the clearState support
Change-Id: I792de0b62c5edbc0e403ac572e94fd208653575d
A 3.x driver is required to connect to Microsoft Azure Cosmos. Upgrading
the target platform accordingly requires further upgrades, including Hamcrest
and JUnit libraries. This, in turn, deprecates or obsoletes numerous APIs,
parts of which that caused compilation *errors* I've replaced by their new
counterparts. Several more warnings still remain and need to be tackled by
replacing the usages to their new counterparts.
in the GWT bundles that had version 2.x but was 3.x. The GWT bundles do
not export servlet API anymore, so everything can consistently be on
servlet version 3.1 that is provided by our jetty server.
clear the state. This is necessary, since test needs a way to create a
well defined state.
The method is published via a Servlet. To avoid data loss, it is
protected by a check of the used database. Only if the database
winddbTest is used, the method call will be dispatched to the
SailingService.
Axel Uhl
Steffen Schaefer
Benjamin Ebling
fmittag
D049941