Re: [cross-project-issues-dev] TM4E planning to start using JavaSE-17 as

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]

Re: [cross-project-issues-dev] TM4E planning to start using JavaSE-17 as BREE soon

From: Mickael Istria <mistria@xxxxxxxxxx>
Date: Tue, 19 Apr 2022 19:05:27 +0200
Delivered-to: cross-project-issues-dev@xxxxxxxxxxx
List-archive: <https://www.eclipse.org/mailman/private/cross-project-issues-dev/>
List-help: <mailto:cross-project-issues-dev-request@eclipse.org?subject=help>
List-subscribe: <https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev>, <mailto:cross-project-issues-dev-request@eclipse.org?subject=subscribe>
List-unsubscribe: <https://www.eclipse.org/mailman/options/cross-project-issues-dev>, <mailto:cross-project-issues-dev-request@eclipse.org?subject=unsubscribe>

Thanks a lot Martin, it's indeed an annoyance.

Is specifying a (older) Gradle version on project a common practice? How does it work in CLI if one uses a newer Gradle install to run some build that defines an older Gradle version?

What are the chances that this bug gets fixed soon enough? (I'm going to ask on the bug as well and link to the discussion).

References:
- [cross-project-issues-dev] TM4E planning to start using JavaSE-17 as BREE soon
  - From: Mickael Istria
- Re: [cross-project-issues-dev] TM4E planning to start using JavaSE-17 as BREE soon
  - From: Martin Lippert

Prev by Date: Re: [cross-project-issues-dev] Apache Maven 3.8.5 is available on all Jenkins instances now
Next by Date: Re: [cross-project-issues-dev] TM4E planning to start using JavaSE-17 as BREE soon
Previous by thread: Re: [cross-project-issues-dev] TM4E planning to start using JavaSE-17 as BREE soon
Next by thread: [cross-project-issues-dev] Two versions of ASM 9.3.0
Index(es):
- Date
- Thread

Breadcrumbs