Jacoco arguments are missing when executing certain tests. This happens when
argLine is being overriden. We had the same problem in Linux Tools. We solved
it by prepending the argLine with ${tycho.testArgLine}. This should help
improving the Code coverage metric in Sonar.
Also update the jacoco version to fix a bug when building with Java 8.
Change-Id: I7f73f40488efc01fc7d643940c1ac0d5950c900d
Signed-off-by: Marc-Andre Laperle <marc-andre.laperle@ericsson.com>
Reviewed-on: https://git.eclipse.org/r/32507
Tested-by: Hudson CI
Reviewed-by: Alvaro Sanchez-Leon <alvsan09@gmail.com>
- Moved tests from separate files to categorized files.
- Introduced node factory in base class.
- Removed use of specific classes, replaced with interaces.
- Moved some tests to apropriate suites.
Change-Id: I71557c0132b888bdc22788f545fec3b03aa732c2
Signed-off-by: Thomas Corbat <tcorbat@hsr.ch>
Reviewed-on: https://git.eclipse.org/r/32251
Tested-by: Hudson CI
Reviewed-by: Sergey Prigogin <eclipse.sprigogin@gmail.com>
Changed ASTRewrite to also accept the root node as valid target for
replacement. Added a test to show the resulting modification store setup
works as expected.
Change-Id: I471d4399690f3a5bb7dcddca45b3f848826b696c
Signed-off-by: Thomas Corbat <tcorbat@hsr.ch>
Reviewed-on: https://git.eclipse.org/r/31747
Tested-by: Hudson CI
Reviewed-by: Sergey Prigogin <eclipse.sprigogin@gmail.com>
Fix for content assist in the context of using declarations:
- No parameter hint for using declaration (template and function)
- No trailing semicolon if one is already present
- Parameter hint for invocation in template arguments
- Space after comma in function suggestions
Some refactoring to content assist test infrastructure.
Change-Id: Id2483ddefe1c35572a9554fdadb0b6416402446a
Signed-off-by: Thomas Corbat <tcorbat@hsr.ch>
Reviewed-on: https://git.eclipse.org/r/30584
Tested-by: Hudson CI
Reviewed-by: Sergey Prigogin <eclipse.sprigogin@gmail.com>
ACBuilder now fails to add a marker if some other marker have no
linumber attribute. Added default line and severity for marker
comparision purposes.
Change-Id: I9c42f660cae08c3303382d8c35aa6404e7130652
Signed-off-by: Alena Laskavaia <elaskavaia.cdt@gmail.com>
Reviewed-on: https://git.eclipse.org/r/31398
Tested-by: Hudson CI
When a statement has been inserted into a replaced compound statement
createModifiedChildArray is called for the new compound statement. The
insert modification is attached to its sibling node. The implementation
for handling this insert was on the parent (compound statement) though.
I moved this (adapted) functionality to handling of the sibling nodes.
With the way insert modifications are stored the previous implementation
cannot have worked. Furthermore, there is no test code which covers the
deleted code.
Change-Id: I9615787177c12a870df7c9663170f38b2c28accb
Signed-off-by: Thomas Corbat <tcorbat@hsr.ch>
Reviewed-on: https://git.eclipse.org/r/30796
Reviewed-by: Sergey Prigogin <eclipse.sprigogin@gmail.com>
Tested-by: Hudson CI
Modified ChangeGeneratorWriterVisitor to cope with nested modifications
as described in the ticket.
Also added some related change generator tests to the corresponding
tests suites.
Refined change to cope with sibling changes too.
Change-Id: Ia04f3d01e50375828588e7fa65e2ec3782c58e79
Signed-off-by: Thomas Corbat <tcorbat@hsr.ch>
Reviewed-on: https://git.eclipse.org/r/30525
Tested-by: Hudson CI
Reviewed-by: Sergey Prigogin <eclipse.sprigogin@gmail.com>
