The amazon Q bundle currently depends on several third-partly dependencies using Require-Bundle:
https://github.com/aws/amazon-q-eclipse/blob/46c5207174871837c4c5586b9fe7bf43eccb6684/plugin/META-INF/MANIFEST.MF#L11-L34
This is fragile, as for 3rd-party components the bundle names are not stable.
For example, between Eclipse 2025-12 and 2026-03, the bundle
org.apache.commons.logging (https://download.eclipse.org/releases/2025-12/202512101000/)
was renamed to
org.apache.commons.commons-logging (https://download.eclipse.org/releases/2026-03/202603111000/plugins/)
making it impossible to install Amazon Q into a fresh Eclipse 2026-03 with only the SimRel update site configured:
Such 3rd-party (apache, gson, ...) libraries should be imported by importing the needed Java packages via Import-Package instead of importing the whole bundle via Require-Bundle to decouple from the bundle name.
The amazon Q bundle currently depends on several third-partly dependencies using
Require-Bundle:https://github.com/aws/amazon-q-eclipse/blob/46c5207174871837c4c5586b9fe7bf43eccb6684/plugin/META-INF/MANIFEST.MF#L11-L34
This is fragile, as for 3rd-party components the bundle names are not stable.
For example, between Eclipse 2025-12 and 2026-03, the bundle
org.apache.commons.logging(https://download.eclipse.org/releases/2025-12/202512101000/)was renamed to
org.apache.commons.commons-logging(https://download.eclipse.org/releases/2026-03/202603111000/plugins/)making it impossible to install Amazon Q into a fresh Eclipse 2026-03 with only the SimRel update site configured:
Such 3rd-party (apache, gson, ...) libraries should be imported by importing the needed Java packages via
Import-Packageinstead of importing the whole bundle viaRequire-Bundleto decouple from the bundle name.