Description Christian Damus 2019-05-07 16:40:16 EDT

This problem is manifest in the latest (7 May 2019) snapshot builds of the RCPTT Runner Maven plug-in at repo.eclipse.org.  The Version field in bugzilla does not have a 2.4.2 value so I had to leave it unspecified.

As described in the linked forum post, I have a private client application that for a long time was based on the Eclipse Platform Oxygen.3 release and tested with RCPTT 2.3.0 in my Maven build.  I am now updating the target platform to Eclipse Platform 2019-03 and because that version of SWT is not supported by RCPTT 2.3.0 and because only the as-yet-unreleased 2.4.2 version supports the ECL commands for interaction with the Nebula Grid control (bug 543732), I have been trying to get my build working with recent 2.4.2 snapshots.

The problem is that my build has been using "injections" to install bundles for testing into my product package, but this injection does not work with the 2.4.2 runner.  These injections are critical to the functioning of my tests:  they include custom ECL commands but also bundles that contribute to my application's extension points in order to test it with simulated user content.

As described in the forum thread, I have a work-around:  defining and building bespoke product packages that "bake in" my injections into a product that otherwise is just like my "real" product, and using these bespoke products as the AUTs for RCPTT Runner.  But that shouldn't be necessary and it bloats my maven build, so I would rather have injections working as in the 2.3.0 release.  As indicated also in that thread, the problem doesn't seem to be in the dependencies of my injection bundles because when I compare the bundles.info generated by RCPTT Runner in the bespoke AUT package and the attempted injection, the only difference is that the injected bundles are missing in the latter.