Александър Куртаков

This looks very promising. What is holding it off ?

@deepika-u Have you looked into what would cause to not use this method in console? It is what I would rather see be done rather than this push/revert.

I haven't found the time to look into it at all. It's the general approach how things should happen in this case that I pointed out.

In general yes - I'm just overloaded with things which leads to huge delays. Would you please rebase on master to fix conflicts?

Having circular dependency between tm4e and platform.releng build is a total no-go. Java 17 is not an issue for me (it's probably time to admit that Java 11 support other...

> > Having circular dependency between tm4e and platform.releng build is a total no-go > > Maybe we have a different understanding of a "circular dependency" but for me a...

Please, the fact that we have many issues doesn't mean we should add more! Let's agree to not make platform build worse than its current terrible state.

So to move the discussion in the right direction - TM4E is used for the editor of .editorconfig files which means that applying/supporting existing .editorconfig files can go in without...

Marketplace entry that has a tag fileextension_editorconfig should be everything needed for MPC to suggest installing the editor.

It's fine to have first draft with ec4j being internal dependency. Before accepting we should have it added to the [target platform](https://github.com/eclipse-platform/eclipse.platform.releng.aggregator/blob/master/eclipse.platform.releng.prereqs.sdk/eclipse-sdk-prereqs.target) referring to the [maven artifact](https://mvnrepository.com/artifact/org.ec4j.core/ec4j-core) directly.