Understanding OSGI Bundle states

Eclipse runs on top of the OSGi runtime, which manages the bundles (components) that make up an application. At any time, each bundle has one of these lifecycle states:

Bundle States:

• Not in the list - If your bundle isn't in the list, then OSGi doesn't know anything about it. See the next section for debugging this problem.
• INSTALLED - This means that OSGi knows about your bundle but there is something wrong and it couldn't resolve. Problems may include thing from missing dependencies to requiring a higher Java VM version than you are running with. To get more information on why your bundle is not resolved try running the diag <bundle id> command, where <bundle id> is your bundle id or bundle symbolic name.
• RESOLVED - If your bundle is resolved but you expected it to be started, then try starting your bundle from the command-line with the start 123 command. If it won't start, then you should get some feedback as to what the problem is.
• <<lazy>> - This means your bundle is resolved and is marked to be lazy started. Everything should be ok.
• ACTIVE - your bundle is resolved and has been started, everything should be working as planned.

(source: OSGi Service Platform – Core Specification)

For example: I want to check the bundle states for my company plugins so I will use the below command.

osgi> ss com.espressif

"Framework is launched."

id State       Bundle

6 RESOLVED    com.espressif.idf.branding_1.2.0.qualifier

7 ACTIVE      com.espressif.idf.core_1.0.0.qualifier

8 STARTING    com.espressif.idf.help_1.0.0.qualifier

9 ACTIVE      com.espressif.idf.launch.serial.core_1.0.0.qualifier

10 ACTIVE      com.espressif.idf.launch.serial.ui_1.0.0.qualifier

11 STARTING    com.espressif.idf.sdk.config.core_1.0.1.qualifier

12 STARTING    com.espressif.idf.sdk.config.ui_1.0.0.qualifier

13 STARTING    com.espressif.idf.terminal.connector_1.0.0.qualifier

14 STARTING    com.espressif.idf.terminal.connector.serial_1.0.0.qualifier

15 ACTIVE      com.espressif.idf.ui_1.0.0.qualifier

721 ACTIVE      com.espressif.idf.debug.gdbjtag.openocd_1.0.0.qualifier

References:

https://wiki.eclipse.org/Where_Is_My_Bundle

GNU MCU Eclipse Plugins

Source code:

https://github.com/eclipse-embed-cdt/eclipse-plugins

It took some time to find this plugin source code since there are multiple GitHub repositories under GNU MCU Eclipse Plugin

Check more on this here https://gnu-mcu-eclipse.github.io/

GNU MCU Eclipse plug-ins getting rebranded as The Eclipse Embedded CDT plug-ins for Arm & RISC-V C/C++ developers

Forcing tycho to build the plugin

Creating forceQualifierUpdate.txt' at the root of the bundle we can force the Tycho to rebuild the plugin.

e.g:
https://github.com/eclipse/eclipse.platform.text/blob/master/org.eclipse.jface.text/forceQualifierUpdate.txt

Check this:
https://wiki.eclipse.org/Platform-releng/Platform_Build_Automated

How to change a default Java version in macOS X

Let me check the current Java version

$ java -version

java version "13.0.2" 2020-01-14

Java(TM) SE Runtime Environment (build 13.0.2+8)

In macOS Java is installed as part of /Library/Java/JavaVirtualMachines folder.

Let me go there.

$ cd /Library/Java/JavaVirtualMachines/

I want to set Java 11 as the default Java version. Let me check what all I've installed in my system.

$ pwd

/Library/Java/JavaVirtualMachines 

$ ls

jdk-11.0.7.jdk jdk-13.0.2.jdk jdk1.8.0_201.jdk

Let me set the default Java version to jdk-11.0.7.jdk

$ export JAVA_HOME=/Library/Java/JavaVirtualMachines/jdk-11.0.7.jdk/Contents/Home/

$ export PATH=$JAVA_HOME/bin:$PATH

The above changes are applicable only for the current shell. To change permanently for all the shells you need set those two lines in the .bash_profile

First, go to the user home directory to run the below command

$ cd ~

$ pwd

/Users/kondal

$vim .bash_profile

Append the above two lines in the .bash_profile at the end, and save and exit.

All set.

Check again!

$ java --version

java 11.0.7 2020-04-14 LTS

Java(TM) SE Runtime Environment 18.9 (build 11.0.7+8-LTS)

Java HotSpot(TM) 64-Bit Server VM 18.9 (build 11.0.7+8-LTS, mixed mode)

Good to go!!

Docker for Eclipse CDT

For my reference

https://github.com/BrainTwister/docker-devel-env

I want to build a docker environment with Eclipse CDT, ESP-IDF Eclipse Plugins, ESP-IDF and it's related ESP-IDF Tools. Probably I can use the above one for reference.

Eclipse User interface guidelines

https://www.eclipse.org/articles/Article-UI-Guidelines/Contents.html

Eclipse CDT based products

For my reference, I found this article very useful.
https://www.eclipse.org/community/eclipse_newsletter/2017/october/article2.php

Espressif joined the league by providing the Eclipse Plugin for ESP-IDF for developing ESP32 IoT applications.

Check here https://github.com/espressif/idf-eclipse-plugin