Hi, @Christian, GEF-Legacy (Draw2d, GEF (MVC), and Zest) is unaffected.
Only the new GEF components depend on JavaFX for rendering and we rely on
e(fx)clipse to make that work.
Best regards,
Matthias
--
Matthias Wienand
B.Sc. Softwaretechnik
Software Engineer
Telefon: +49 231 9860 202
Note that e(fx)clipse withdrawing from the Simultaneous Release does not
mean that the content produced by the project cannot be included in the
repository. Another project can pull in their some subset of the project's
content, but that project must take responsibility for that content. It's
Hi, @Matthias will this affect Draw2d parts as well?Thanks Christian
Am 01.02.19 um 19:29 schrieb Matthias Wienand:
> Yes, GEF does depend on e(fx)clipse. I will try to catch up with the
> discussions. I hope we can still deliver GEF via SimRel, but this does not
> sound promising.
>
> Best
Hi,
Yes, GEF does depend on e(fx)clipse. I will try to catch up with the
discussions. I hope we can still deliver GEF via SimRel, but this does not
sound promising.
Best regards,
Matthias
--
Matthias Wienand
B.Sc. Softwaretechnik
Software Engineer
Telefon: +49 231 9860 202
Telefax: +49 231
If you're dropping out, please push a Gerrit review that removes your
project's aggrcon file.
If anybody else depends on e(fx)clipse (I think that the Eclipse GEF
project has a dependency), please speak up. We need to start the mitigation
process ASAP.
Thanks,
Wayne
On Fri, Feb 1, 2019 at 6:33
Hi,
e(fx)clipse will drop from the release train. Our problem is exactly as
described as described by Wayne in "Preparing for 2019-03M2..."
We simply don't have the cycles to test our IDE-Contribution good enough
causing trouble and casting a damning light on the Eclipse IDE.
People will be
