Eclipse Community Forums: RCP Testing Tool » Two Blocker Issues with RCPTT

Home » Eclipse Projects » RCP Testing Tool » Two Blocker Issues with RCPTT

Two Blocker Issues with RCPTT [message #1799620]

Tue, 11 December 2018 04:28

Eclipse User

Hi,

I have to raise a question about the general project maintenance state of the RCPTT project.
The question is whether adopters can rely on some basic maintenance being done in RCPTT.

Backgound is that there are currently two blocker issues with RCPTT which prevent all users to use RCPTT with newer versions of Eclipse.

RCPTT is not running with 2018-09
https://bugs.eclipse.org/bugs/show_bug.cgi?id=538719

RCPTT is not working with e4 applications
https://bugs.eclipse.org/bugs/show_bug.cgi?id=441067

I think nobody can expect free 24/7 support from an open source project. However, it would be good to have a clear communication about what adopters can expect and when. Do you plan to continuously support new 3.x versions? Will you ever complete the e4 support?

Please let me add, that I like RCPTT a lot. However, as it is a central tool, if you use it in projects, it is essential to know about its state.

Thank you for a statement and best regards,
Jonas

Re: Two Blocker Issues with RCPTT [message #1799773 is a reply to message #1799620]

Thu, 13 December 2018 06:49

Eclipse User

Hello.
Thank you for your concern and interest.

The switch to 2018-09 is going on in https://git.eclipse.org/r/#/c/130963/
Unfortunately we found a regress - lazily populated trees are not populated during RCPTT interactions.
Estimation is fuzzy - it may take anywhere from 3 days to weeks of work (lazy tree handling is one of the more complicated parts in RCPTT codebase). Finer estimation will be available once we continue working on the task.
We could suggest to use build artifacts from the Gerrit change builds. If you do not test lazily populated tree (like Variables view in Debug perspective), it would just work.

Latest build artifacts: https://ci.eclipse.org/rcptt/job/rcptt-all-gerrit/1484/artifact/repository/full/target/products/

We will deal with it once we have resolved more urgent issues. I would imagine this happen in January.

We did not attempt 2018-12 migration yet.

Support for pure E4 applications requires enormous effort (half an year of work), has very low priority do to absence of financial backing and is not expected anytime soon.

Re: Two Blocker Issues with RCPTT [message #1799783 is a reply to message #1799773]

Thu, 13 December 2018 08:07

Eclipse User

Hi Vasili,

thank you very much for the detailed answer!

Best regards,
Jonas

Re: Two Blocker Issues with RCPTT [message #1799968 is a reply to message #1799773]

Tue, 18 December 2018 03:43

Eclipse User

Hi Vasili,

I want to clarify one moment. You mentioned that migration to 2018-12 is not started yet, but nightly build name is already changed to "2.4.0.201812180014 Nightly". Doesn't that mean that there are some plans or timeline for this migration? If so, can you please share it to me?

It's kind of important question for us because our AUT is based on 1018-12, all tests are freezed and we need to decide shall we wait for RCPTT migration or it will be to long and we should try to do it on out side.
Thanks in advance!

Previous Topic:	rcptt-maven-plugin: Problem with " in vmArgs
Next Topic:	RCPTT Maven plugin and Tycho

Goto Forum:

-=] Back to Top [=-

Current Time: Sat Apr 19 20:31:21 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter