Hi, Team,
I have a JUnit test that is failing in Gerrit [1] because of a problem in our Target Platform’s adherence to the 1.5 version of the Eclipse Databinding API. The test fails because of an exception that occurs in the rendering of control by the EnumComboViewerSWTRenderer. The fact that this renderer is involved in the test scenario is entirely irrelevant to the purpose of the test, but nonetheless it bombs the test.
The problem is that this renderer attempts to load the ISideEffect interface that was introduced in Databindings 1.6, and so is not available in the 1.5 version that is configured in the Target Platform for the Maven build. The consequent ClassNotFoundException bombs the test. Strangely, in my development environment configured with the ecp.target, the PDE can “see” the 1.6 versions of the Databindings bundles and so running the test in my development environment works fine.
So, the question for the team is:
- why is the Maven build pinned to this very old 1.5 version of the Databindings API? It is long since out of service (it was released in 2015!)
- would there be objection to my updating the target platform to use a more modern Databindings?
If I don’t update the target platform, I will have to update my test to render views for objects that don’t require renderers with dependency on the ISideEffect API. But I worry that this would only postpone the inevitable: it won’t be long before we need to run tests that have no option but to use ISideEffect-dependent code because it’s that code that they test (I’m frankly surprised that we don’t already have such tests — surely this code that requires ISideEffect is covered by the tests?).
