Where does eclipse CDT stores CMake toolchain information?

CDT stores cmake toolchain information as part of org.eclipse.cdt.cmake.core.prefs file.

/Users/kondal/runtime-EclipseApplication6/.metadata/.plugins/org.eclipse.core.runtime/.settings/org.eclipse.cdt.cmake.core.prefs

For example, here is the content of the file 

cmakeToolchains/14/__path=/Users/kondal/esp/esp-idf/tools/cmake/toolchain-esp32.cmake

cmakeToolchains/14/cdt.toolChain.id=gcc-xtensa-/Users/kondal/esp/xtensa-esp32-elf/bin/xtensa-esp32-elf-gcc

cmakeToolchains/14/cdt.toolChain.type=org.eclipse.cdt.build.gcc

cmakeToolchains/n=15

eclipse.preferences.version=1

To understand more how eclipse store preferences:
https://gnu-mcu-eclipse.github.io/developer/eclipse/runtime-preferences/

Where can I find the eclipse store preferences in the file system

Eclipse stores the preferences in the workspace of your application in the.metadata/.plugins/org.eclipse.core.runtime/.settings/ directory in the <nodePath>.prefs file

For example, for CDT build environment variables stored in here:

.metadata/.plugins/org.eclipse.core.runtime/.settings/org.eclipse.cdt.core.pref

x

Java processes and streams and avoiding blocks

One of the best resource on managing the streams in Java
https://wiki.sei.cmu.edu/confluence/display/java/FIO07-J.+Do+not+let+external+processes+block+on+IO+buffers

Checklist of refactoring done right way

https://refactoring.guru/refactoring/how-to

security certificates of a jar file

$ jarsigner -verify -verbose -certs  /Eclipse/plugins/com.espressif.core_1.0.0.jar 

Design process and some famous design models

Design Thinking Model

Double Diamond Model

https://www.designcouncil.org.uk/news-opinion/design-process-what-double-diamond

Google Design Sprint

The Design Sprint follows six phases: Understand, Define, Sketch, Decide, Prototype, and Validate.

https://designsprintkit.withgoogle.com/methodology/overview

Should we migrate projects from Java 8 to Java 9 or 10

If you're on Java 8, you might be thinking should we migrate the projects from Java 8 to Java 9 or 10?

Big NO!!

It doesn’t worth the effort. It’s better if you migrate your projects directly to Java 11 which is an LTS version.

Java 9 and Java 10 are non-LTS versions.

“For product releases after Java SE 8, Oracle will designate a release, every three years, as a Long-Term-Support (LTS) release. Java SE 11 (18.9 LTS) is an LTS release. For the purposes of Oracle Premier Support, non‑LTS releases are considered a cumulative set of implementation enhancements of the most recent LTS release. Once a new feature release is made available, any previous non‑LTS release will be considered superseded. For example, Java SE 9 was a non‑LTS release and immediately superseded by Java SE 10 (also non‑LTS), Java SE 10 in turn is immediately superseded by Java SE 11. Java SE 11 however is an LTS release, and therefore Oracle Customers will receive Oracle Premier Support and periodic update releases, even after Java SE 12 is released.”

For long-term support, Oracle is recommending remaining on Java 8 or move to Java 11.  Refer to the following:

https://www.oracle.com/technetwork/java/eol-135779.html

Java 8 Release support:

Premier support: March 2022

Extended support: March 2025

Java 9:

Premier support: March 2018

Extended support: Not available

Java 10:

Premier support: Sept 2018

Extended support: Not available

Java 11:

Premier support: Sept 2023
Extended support: Sept 2026