Re: [cft-dev] CFT 1.0 JRebel integration breaking change

[Nieraj Singh <nsingh@xxxxxxxxxx>]

I've added my own comments. Looking at the code and Elson's suggestions, it seems very minimal work and very localised to just the JRebel support in CFT, to support both old and new JRebel plugins.

Martin, please let us know your thoughts on this, if we should aim for RC2 (tomorrow, Wednesday, May 25) or RC3, or postpone after 1.0 is released, since we also don't know how many users actually user JRebel integration, especially outside of STS (e.g. JEE package only).

Thank you.

On Tue, May 24, 2016 at 2:10 PM, Elson Yuen <eyuen@xxxxxxxxxx> wrote:

Given that we know JRebel support will be broken on the new release, I think we should go ahead on making the change in RC3. I added some comments to the bug for compatibility concerns. It should still be fairly easy and straight forward to implement even if we decide to make it compatible.

Regards,
Elson

-----------------------------------------------------------------
Elson Yuen, P.Eng.
WebSphere Server Tools and Bluemix Tools Architect
IBM Toronto Lab
Tel: (905) 413-2689, T/L: 313-2689


Nieraj Singh ---05/24/2016 02:48:47 PM---We recently got notified that the new JRebel Eclipse plugin , to be release early June, will have br

From: Nieraj Singh <nsingh@xxxxxxxxxx>
To: cft developer discussions <cft-dev@xxxxxxxxxxx>, Elson Yuen/Toronto/IBM@IBMCA, Martin Lippert <mlippert@xxxxxxxxxx>
Date: 05/24/2016 02:48 PM
Subject: CFT 1.0 JRebel integration breaking change

---

We recently got notified that the new JRebel Eclipse plugin , to be
release early June, will have breaking changes that will break JRebel
integration in CFT.

https://bugs.eclipse.org/bugs/show_bug.cgi?id=494475

Do we want to fix this for CFT 1.0 RC3? It is a very simple change,
and only affects the JRebel integration, and no other core component
that has already been tested. Details are in the bugzilla above.

If so, I'm cc'ing PMC (Martin) for additional approval and comments.