Re: [eclipse-pmc] Move of classes from o.e.jface.text to o.e.text

["Daniel Megert" <daniel_megert@xxxxxxxxxx>]

I prefer the second
approach as it's less risky and better to have the right package name (no
'jface' in the name). However, the new code must be an exact copy, otherwise
clients using the deprecated types might get broken. I am also fine to
not deprecate the old types as suggested in https://bugs.eclipse.org/bugs/show_bug.cgi?id=558350#c7by Alex.

Dani



From:
       Aleksandar
Kurtakov <akurtako@xxxxxxxxxx>
To:
       eclipse-pmc@xxxxxxxxxxx
Date:
       27.03.2020
12:12
Subject:
       [EXTERNAL]
[eclipse-pmc] Move of classes from o.e.jface.text to o.e.text
Sent
by:        eclipse-pmc-bounces@xxxxxxxxxxx

---

This request comes from https://bugs.eclipse.org/bugs/show_bug.cgi?id=558350and Mickael proposal to move classes is the easiest in the current situation,
with the bump of o.e.text version by x.y+6 to match jface.text so cases
doing package imports satisfy again.
Alternatively, we move the classes to
o.e.text.rules and make the classes in jface.text deprecated and just redirecting
to the o.e.text.rules so we do not introduce one more split package and
knowing that is a no-go for JPMS (which we don't use right now but shouldn't
make it even harder for the future).

-- 
Alexander Kurtakov
Red Hat Eclipse Team_______________________________________________
eclipse-pmc mailing list
eclipse-pmc@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/eclipse-pmc