Reverting all previous commits of this temporary branch

Change-Id: Ie263f833653f78115a041a50341f12688bafc01e
Signed-off-by: Marc Khouzam <marc.khouzam@ericsson.com>
Bug 455992 - MIRunControlTest.getExecutionContexts fails when run in
remote mode 

Change-Id: I869a7496e63380f3839d641105fa29fc0c1c3b74
Signed-off-by: Marc Khouzam <marc.khouzam@ericsson.com>
Reviewed-on: https://git.eclipse.org/r/38692
Tested-by: Hudson CI
Revert "Bug 451929 - Leverage p2 ability to express native packages"

This is breaking downstream builds.

This reverts commit 18e6101a53d99969f9dff1fdbc95debb18983390.

Change-Id: I5dd2ee129518757866ab832c683b648d13b07b83
Reviewed-on: https://git.eclipse.org/r/38594
Tested-by: Hudson CI
Reviewed-by: Doug Schaefer <dschaefer@qnx.com>
Typos

Change-Id: I78bd2f2f640dcac283bf0bc4259d6acf3080a3c2
Signed-off-by: Marc Khouzam <marc.khouzam@ericsson.com>
Bug 456083 - Wrong preference scope causes test dependencies

Change-Id: I36b91e6c0c8180919e033d7630db92f148b69214
Signed-off-by: Marc Khouzam <marc.khouzam@ericsson.com>
Reviewed-on: https://git.eclipse.org/r/38721
Tested-by: Hudson CI
Cosmetics.
Adjusted method visibility.
Cosmetics.
Bug 456099 - Renaming a class should also rename related files
Avoid gdb bug in StepIntoSelectionTests for gdb <= 7.3

When a breakpoint is set directly at the start of a function, and you step
into that function, gdb <= 7.3 will generate a "stopped" event with two
reason fields. The first to indicate that the step range ended and the
other to indicate that a breakpoint was hit. While this is not really
correct from gdb to include the same field twice in a single event,
the implementation of MIRunControlEventProcessor_7_0 will generate two
distinct MIStoppedEvent events. This confuses the step-into-selection
mechanism, who will issue two finish/step-return instead of one.

For all gdbs, we will have a test where the breakpoint is a not at the
function entry.

Then, for gdb > 7.3, we will have the same test but with the breakpoint
at the function entry, to test that particular case. This case is known
to be broken with gdb <= 7.3 (rather old) and will stay that way unless
somebody feels like fixing it.

So, for both:

- atDoubleMethodStopAtBreakpoint
- atDoubleMethodSkipBreakpoint

I extracted the code in a common function which takes in parameter the
line to set the breakpoint at.

Change-Id: I2ae4bc527afe0ab195e9b066279ed92f74d652f3
Signed-off-by: Simon Marchi <simon.marchi@polymtl.ca>
Reviewed-on: https://git.eclipse.org/r/38717
Tested-by: Hudson CI
Reviewed-by: Marc Khouzam <marc.khouzam@ericsson.com>
Tested-by: Marc Khouzam <marc.khouzam@ericsson.com>
Trying out 7.1 testsuite

Change-Id: If50d9f33621790d054e25a416ba0ea6e4adbc504
Signed-off-by: Marc Khouzam <marc.khouzam@ericsson.com>