mirrors/cdt
1
0
Fork 0
mirror of https://github.com/eclipse-cdt/cdt synced 2025-07-28 11:25:35 +02:00
Code Issues Wiki Activity
cdt/debug/org.eclipse.cdt.debug.application/META-INF/MANIFEST.MF

38 lines
1.4 KiB
Text
Raw Normal View History

Add CDT Standalone Debugger - add org.eclipse.cdt.debug.application plugin which supports running CDT debugger as Eclipse application - add org.eclipse.cdt.debug.application.docs plugin which is the modified CDT docs - add org.eclipse.cdt.debug.standalone-feature which bundles the two aforementioned plugins - add org.eclipse.cdt.debug.standlone.source-feature Change-Id: I1a1ae855ab3912e678b7d9e3465e2fbbfe949e13 Reviewed-on: https://git.eclipse.org/r/25845 Reviewed-by: Jeff Johnston <jjohnstn@redhat.com> Tested-by: Jeff Johnston <jjohnstn@redhat.com>
2014-05-01 14:42:16 -04:00
Manifest-Version: 1.0
Bundle-ManifestVersion: 2
Bundle-Name: %bundleName
Bundle-SymbolicName: org.eclipse.cdt.debug.application;singleton:=true
Prepare repo for 11.7.0 development (#813)
2024-06-05 13:19:53 -04:00
Bundle-Version: 11.7.0.qualifier
Add CDT Standalone Debugger - add org.eclipse.cdt.debug.application plugin which supports running CDT debugger as Eclipse application - add org.eclipse.cdt.debug.application.docs plugin which is the modified CDT docs - add org.eclipse.cdt.debug.standalone-feature which bundles the two aforementioned plugins - add org.eclipse.cdt.debug.standlone.source-feature Change-Id: I1a1ae855ab3912e678b7d9e3465e2fbbfe949e13 Reviewed-on: https://git.eclipse.org/r/25845 Reviewed-by: Jeff Johnston <jjohnstn@redhat.com> Tested-by: Jeff Johnston <jjohnstn@redhat.com>
2014-05-01 14:42:16 -04:00
Bundle-Activator: org.eclipse.cdt.debug.application.Activator
Bundle-Vendor: %provider
Require-Bundle: org.eclipse.ui,
org.eclipse.core.runtime,
org.eclipse.cdt.debug.ui;bundle-version="7.3.0",
org.eclipse.cdt.dsf;bundle-version="2.4.0",
org.eclipse.cdt.dsf.gdb;bundle-version="4.2.0",
org.eclipse.cdt.dsf.gdb.ui;bundle-version="2.4.0",
org.eclipse.cdt.dsf.ui;bundle-version="2.4.0",
org.eclipse.cdt.gdb;bundle-version="7.0.0",
org.eclipse.cdt.gdb.ui;bundle-version="7.0.0",
org.eclipse.cdt.launch;bundle-version="7.1.0",
org.eclipse.ui.ide,
org.eclipse.cdt.core,
org.eclipse.cdt.managedbuilder.core;bundle-version="8.2.1",
org.eclipse.cdt.managedbuilder.gnu.ui;bundle-version="8.2.0",
org.eclipse.cdt.debug.core,
Use the bundle providing javax.activation package in simrel (#626) Because javax.activation 1.2.2.v20221203-1659 is in SimRel (for now) it gets picked by p2 over jakarta.activation-api 1.2.2 which provides the same packages. As and when we update to Jave EE 9 (IIUC) we should be able to solve this in a cleaner way and not rely on the old orbit bundles. Also, if and when all projects contributing to simrel remove 1.2.2.v20221203-1659 then we can change too. The other option is to try to force the jakarta.activation-api 1.2.2 into simrel and the EPP packages, but if we accidentally end up with both in a product then other things don't work, e.g. like this error: <details> <summary>frame work error details</summary> ```java !ENTRY org.eclipse.cdt.debug.application 4 0 2023-11-20 15:06:47.456 !MESSAGE FrameworkEvent ERROR !STACK 0 org.osgi.framework.BundleException: Could not resolve module: org.eclipse.cdt.debug.application [101] Unresolved requirement: Require-Bundle: org.eclipse.cdt.dsf; bundle-version="2.4.0" -> Bundle-SymbolicName: org.eclipse.cdt.dsf; bundle-version="2.12.0.202211062329"; singleton:="true" org.eclipse.cdt.dsf [116] No resolution report for the bundle. Unresolved requirement: Require-Bundle: org.eclipse.cdt.dsf.ui; bundle-version="2.4.0" -> Bundle-SymbolicName: org.eclipse.cdt.dsf.ui; bundle-version="2.7.200.202311031553"; singleton:="true" org.eclipse.cdt.dsf.ui [119] Unresolved requirement: Require-Bundle: org.eclipse.cdt.dsf; bundle-version="2.0.0" -> Bundle-SymbolicName: org.eclipse.cdt.dsf; bundle-version="2.12.0.202211062329"; singleton:="true" Unresolved requirement: Require-Bundle: org.eclipse.cdt.gdb; bundle-version="7.0.0" -> Bundle-SymbolicName: org.eclipse.cdt.gdb; bundle-version="7.2.100.202303140100"; singleton:="true" org.eclipse.cdt.gdb [121] No resolution report for the bundle. Unresolved requirement: Require-Bundle: org.eclipse.cdt.dsf.gdb.ui; bundle-version="2.4.0" -> Bundle-SymbolicName: org.eclipse.cdt.dsf.gdb.ui; bundle-version="2.8.300.202309151124"; singleton:="true" org.eclipse.cdt.dsf.gdb.ui [118] Unresolved requirement: Require-Bundle: org.eclipse.cdt.dsf.ui -> Bundle-SymbolicName: org.eclipse.cdt.dsf.ui; bundle-version="2.7.200.202311031553"; singleton:="true" Unresolved requirement: Require-Bundle: org.eclipse.cdt.dsf.gdb; bundle-version="[7.0.0,8.0.0)" -> Bundle-SymbolicName: org.eclipse.cdt.dsf.gdb; bundle-version="7.1.200.202309151124"; singleton:="true" org.eclipse.cdt.dsf.gdb [117] Unresolved requirement: Require-Bundle: org.eclipse.cdt.dsf -> Bundle-SymbolicName: org.eclipse.cdt.dsf; bundle-version="2.12.0.202211062329"; singleton:="true" Unresolved requirement: Require-Bundle: org.eclipse.cdt.native.serial; bundle-version="1.1.100" -> Bundle-SymbolicName: org.eclipse.cdt.native.serial; bundle-version="11.4.0.202311201859" org.eclipse.cdt.native.serial [141] No resolution report for the bundle. Unresolved requirement: Require-Bundle: org.eclipse.cdt.gdb; bundle-version="7.0.0" -> Bundle-SymbolicName: org.eclipse.cdt.gdb; bundle-version="7.2.100.202303140100"; singleton:="true" Unresolved requirement: Require-Bundle: org.eclipse.cdt.native.serial; bundle-version="1.1.100" -> Bundle-SymbolicName: org.eclipse.cdt.native.serial; bundle-version="11.4.0.202311201859" Unresolved requirement: Require-Bundle: org.eclipse.tm.terminal.control; bundle-version="4.0.0" -> Bundle-SymbolicName: org.eclipse.tm.terminal.control; bundle-version="5.5.100.202311142253"; singleton:="true" org.eclipse.tm.terminal.control [506] No resolution report for the bundle. Unresolved requirement: Require-Bundle: org.eclipse.cdt.dsf -> Bundle-SymbolicName: org.eclipse.cdt.dsf; bundle-version="2.12.0.202211062329"; singleton:="true" Unresolved requirement: Require-Bundle: jakarta.activation-api; bundle-version="[1.2.2,2.0.0)" -> Bundle-SymbolicName: jakarta.activation-api; bundle-version="1.2.2" jakarta.activation-api [30] No resolution report for the bundle. Unresolved requirement: Require-Bundle: org.eclipse.cdt.dsf.gdb; bundle-version="4.2.0" -> Bundle-SymbolicName: org.eclipse.cdt.dsf.gdb; bundle-version="7.1.200.202309151124"; singleton:="true" Unresolved requirement: Require-Bundle: org.eclipse.cdt.gdb.ui; bundle-version="7.0.0" -> Bundle-SymbolicName: org.eclipse.cdt.gdb.ui; bundle-version="7.2.0.202211062329"; singleton:="true" org.eclipse.cdt.gdb.ui [122] No resolution report for the bundle. Bundle was not resolved because of a uses constraint violation. org.apache.felix.resolver.reason.ReasonException: Uses constraint violation. Unable to resolve resource org.eclipse.cdt.debug.application [osgi.identity; osgi.identity="org.eclipse.cdt.debug.application"; type="osgi.bundle"; version:Version="11.4.0.202311201855"; singleton:="true"] because it is exposed to package 'javax.activation' from resources jakarta.activation-api [osgi.identity; osgi.identity="jakarta.activation-api"; type="osgi.bundle"; version:Version="1.2.2"] and javax.activation [osgi.identity; osgi.identity="javax.activation"; type="osgi.bundle"; version:Version="1.2.2.v20221203-1659"] via two dependency chains. Chain 1: org.eclipse.cdt.debug.application [osgi.identity; osgi.identity="org.eclipse.cdt.debug.application"; type="osgi.bundle"; version:Version="11.4.0.202311201855"; singleton:="true"] require: (&(osgi.wiring.bundle=jakarta.activation-api)(&(bundle-version>=1.2.2)(!(bundle-version>=2.0.0)))) | provide: osgi.wiring.bundle: jakarta.activation-api jakarta.activation-api [osgi.identity; osgi.identity="jakarta.activation-api"; type="osgi.bundle"; version:Version="1.2.2"] Chain 2: org.eclipse.cdt.debug.application [osgi.identity; osgi.identity="org.eclipse.cdt.debug.application"; type="osgi.bundle"; version:Version="11.4.0.202311201855"; singleton:="true"] require: (&(osgi.wiring.bundle=jakarta.xml.bind-api)(&(bundle-version>=2.3.3)(!(bundle-version>=3.0.0)))) | provide: osgi.wiring.bundle; bundle-version:Version="2.3.3"; osgi.wiring.bundle="jakarta.xml.bind-api" jakarta.xml.bind-api [osgi.identity; osgi.identity="jakarta.xml.bind-api"; type="osgi.bundle"; version:Version="2.3.3"] import: (osgi.wiring.package=javax.activation) | export: osgi.wiring.package: javax.activation javax.activation [osgi.identity; osgi.identity="javax.activation"; type="osgi.bundle"; version:Version="1.2.2.v20221203-1659"] at org.eclipse.osgi.container.Module.start(Module.java:463) at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel$2.run(ModuleContainer.java:1852) at org.eclipse.osgi.internal.framework.EquinoxContainerAdaptor$1$1.execute(EquinoxContainerAdaptor.java:136) at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1845) at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1786) at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1750) at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1672) at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1) at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:234) at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:345) ``` </details> The underlying problem here is that the debug application's "product" that gets converted to a config.ini at CDT build time doesn't expose its dependencies fully to p2, so we end up with a built product in EPP that doesn't have everything listed in config.ini. There is significant maintenance overhead and it is growing to keeping standalone as it is now working. Other options should probably be considered, such as using the config of the full product when launching. Fixes #591
2023-11-21 13:57:24 -05:00
org.eclipse.ui.workbench
Update to Java 17 as BREE. Fixes #80
2022-10-01 19:59:59 -04:00
Bundle-RequiredExecutionEnvironment: JavaSE-17
Add CDT Standalone Debugger - add org.eclipse.cdt.debug.application plugin which supports running CDT debugger as Eclipse application - add org.eclipse.cdt.debug.application.docs plugin which is the modified CDT docs - add org.eclipse.cdt.debug.standalone-feature which bundles the two aforementioned plugins - add org.eclipse.cdt.debug.standlone.source-feature Change-Id: I1a1ae855ab3912e678b7d9e3465e2fbbfe949e13 Reviewed-on: https://git.eclipse.org/r/25845 Reviewed-by: Jeff Johnston <jjohnstn@redhat.com> Tested-by: Jeff Johnston <jjohnstn@redhat.com>
2014-05-01 14:42:16 -04:00
Bundle-Localization: plugin
Bundle-ActivationPolicy: lazy
Eclipse-BundleShape: dir
Import-Package: org.eclipse.cdt.core.model,
org.eclipse.cdt.debug.core,
org.eclipse.cdt.debug.core.executables,
org.eclipse.core.resources,
org.eclipse.debug.core,
org.eclipse.debug.ui,
org.eclipse.debug.ui.actions
o.e.cdt.debug.application should export its packages Change-Id: Ifeb5f78d776eca939187738180434000b0b2f8b2 Signed-off-by: Marc-Andre Laperle <marc-andre.laperle@ericsson.com>
2015-01-29 16:14:23 -05:00
Export-Package: org.eclipse.cdt.debug.application,
org.eclipse.cdt.internal.debug.application;x-internal:=true
Bug 540610 - Add Automatic-Module-Name header Change-Id: Ia990b24469751050dd9ec8f9b5550804816308b3 Signed-off-by: Karsten Thoms <karsten.thoms@itemis.de>
2018-10-30 15:29:24 +01:00
Automatic-Module-Name: org.eclipse.cdt.debug.application
Reference in a new issue Copy permalink