On Tue, Apr 19, 2022 at 8:35 PM Torbjorn SVENSSON via cross-project-issues-dev <cross-project-issues-dev@eclipse.org> wrote:
> Hello, > Hi, > What you are talking about here is more or less requiring anyone using > SimRel to also move to a JRE 17. Not directly (SimRel can still use older versions of TM4E), but yes, I guess it can become the beginning of a trend for many projects and ultimately SimRel moving to JRE 17. Downstream projects/products that have different requirements from what SimRel decides to provide will have to deal with them on their hand, eg composing versions in their .target. > I think that's okay to do, but there should be some heads up for this type > of change as it can cause major problem for our downstream consumers. > This is kind of a 1st heads up ;) My 2 cents is that the newest BREE allowed in SimRel should be the same > version that is said to be the required JRE version to run the Eclipse IDE > (AFAIK, that's JRE 11 ATM). Eclipse IDE can currently run with JRE 11, but the vast majority of users now do get JustJ from EPP packages; and that is currently Java 18. But overall, it is still totally acceptable for some projects to stick to older Java while some other move to newer.
_______________________________________________ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
