mirrors/cdt
1
0
Fork 0
mirror of https://github.com/eclipse-cdt/cdt synced 2025-08-02 22:05:44 +02:00
Code Issues Wiki Activity
cdt/dsf-gdb/org.eclipse.cdt.dsf.gdb.multicorevisualizer.ui/META-INF/MANIFEST.MF

28 lines
1.5 KiB
Text
Raw Normal View History

Bug 335027: Visualizer View feature. Initial contribution.
2012-02-10 13:10:03 -05:00
Manifest-Version: 1.0
Bundle-ManifestVersion: 2
Bug 540373: Fix trailing whitespace in MANIFEST.MFs Change-Id: I818e939ec4667bea4c7bcd5cd3c1af1a273ca0ce
2018-11-23 13:35:39 +00:00
Bundle-Name: %pluginName
Bug 335027: Visualizer View feature. Initial contribution.
2012-02-10 13:10:03 -05:00
Bundle-Vendor: %providerName
Bundle-SymbolicName: org.eclipse.cdt.dsf.gdb.multicorevisualizer.ui;singleton:=true
[releng] Require target platform bundles as minimum version Using: ``` mvn org.eclipse.tycho.extras:tycho-version-bump-plugin:4.0.12:update-manifest ``` and then multiple iterations to bump the bundle-version: ``` mvn verify org.eclipse.tycho:tycho-versions-plugin:4.0.12:bump-versions -Dtycho.bump-versions.increment=100 -DskipDoc=true -DskipTests=true -P baseline-compare-and-replace -fae -Djgit.dirtyWorkingTree-cdtDefault=warning ``` Make sure bounds of all dependencies match what we built against. This prevents issues such as Bug 536448 from recurring. In 2025-06 there are a number of Eclipse Platform changes that make CDT susceptible to these types of issues again. Note that this change is similar to previous iterations, such as 1087dc5f2255b8befa31e6e0cf98e72d9483ceed, but with the automatation we can now apply this to *all* bundles. In addition, with the tighter version constraints, building from simrel repo for the jniheader (releng/scripts/do_rebuild_natives.sh) is no longer sufficient. This speedup has been removed as it was probably incorrect to have by default. The api filters were introduced because some bundles are re-exported. Those re-exported bundle requirements mean that technically we need to bump the version, but in reality we effectively required the range as now documented anyway, so doing a major version bump is unneeded.
2025-05-18 15:37:50 -04:00
Bundle-Version: 1.3.600.qualifier
Bug 335027: Visualizer View feature. Initial contribution.
2012-02-10 13:10:03 -05:00
Bundle-Activator: org.eclipse.cdt.dsf.gdb.multicorevisualizer.internal.ui.MulticoreVisualizerUIPlugin
Bundle-Localization: plugin
[releng] Require target platform bundles as minimum version Using: ``` mvn org.eclipse.tycho.extras:tycho-version-bump-plugin:4.0.12:update-manifest ``` and then multiple iterations to bump the bundle-version: ``` mvn verify org.eclipse.tycho:tycho-versions-plugin:4.0.12:bump-versions -Dtycho.bump-versions.increment=100 -DskipDoc=true -DskipTests=true -P baseline-compare-and-replace -fae -Djgit.dirtyWorkingTree-cdtDefault=warning ``` Make sure bounds of all dependencies match what we built against. This prevents issues such as Bug 536448 from recurring. In 2025-06 there are a number of Eclipse Platform changes that make CDT susceptible to these types of issues again. Note that this change is similar to previous iterations, such as 1087dc5f2255b8befa31e6e0cf98e72d9483ceed, but with the automatation we can now apply this to *all* bundles. In addition, with the tighter version constraints, building from simrel repo for the jniheader (releng/scripts/do_rebuild_natives.sh) is no longer sufficient. This speedup has been removed as it was probably incorrect to have by default. The api filters were introduced because some bundles are re-exported. Those re-exported bundle requirements mean that technically we need to bump the version, but in reality we effectively required the range as now documented anyway, so doing a major version bump is unneeded.
2025-05-18 15:37:50 -04:00
Require-Bundle: org.eclipse.ui;bundle-version="[3.207.200,4)",
Explicitly use Platform's M3 I-build Since M3 was published, platform had upped version of org.eclipse.core.runtime. See https://github.com/eclipse-cdt/cdt/pull/1165#issuecomment-2892408192
2025-05-19 18:16:01 -04:00
org.eclipse.core.runtime;bundle-version="[3.33.0,4)",
[releng] Require target platform bundles as minimum version Using: ``` mvn org.eclipse.tycho.extras:tycho-version-bump-plugin:4.0.12:update-manifest ``` and then multiple iterations to bump the bundle-version: ``` mvn verify org.eclipse.tycho:tycho-versions-plugin:4.0.12:bump-versions -Dtycho.bump-versions.increment=100 -DskipDoc=true -DskipTests=true -P baseline-compare-and-replace -fae -Djgit.dirtyWorkingTree-cdtDefault=warning ``` Make sure bounds of all dependencies match what we built against. This prevents issues such as Bug 536448 from recurring. In 2025-06 there are a number of Eclipse Platform changes that make CDT susceptible to these types of issues again. Note that this change is similar to previous iterations, such as 1087dc5f2255b8befa31e6e0cf98e72d9483ceed, but with the automatation we can now apply this to *all* bundles. In addition, with the tighter version constraints, building from simrel repo for the jniheader (releng/scripts/do_rebuild_natives.sh) is no longer sufficient. This speedup has been removed as it was probably incorrect to have by default. The api filters were introduced because some bundles are re-exported. Those re-exported bundle requirements mean that technically we need to bump the version, but in reality we effectively required the range as now documented anyway, so doing a major version bump is unneeded.
2025-05-18 15:37:50 -04:00
org.eclipse.cdt.dsf;bundle-version="[2.12.200,3)",
org.eclipse.cdt.dsf.ui;bundle-version="[2.7.500,3)",
org.eclipse.cdt.dsf.gdb;bundle-version="[7.1.500,8)",
org.eclipse.cdt.ui;bundle-version="[9.0.100,10)",
org.eclipse.cdt.visualizer.core;bundle-version="[1.2.200,2)",
org.eclipse.cdt.visualizer.ui;bundle-version="[1.5.400,2)",
org.eclipse.debug.ui;bundle-version="[3.18.800,4)",
org.eclipse.cdt.core;bundle-version="[9.1.0,10)",
org.eclipse.cdt.debug.ui;bundle-version="[8.5.700,9)"
Bug 335027: Visualizer View feature. Initial contribution.
2012-02-10 13:10:03 -05:00
Bundle-ActivationPolicy: lazy
Update to Java 17 as BREE. Fixes #80
2022-10-01 19:59:59 -04:00
Bundle-RequiredExecutionEnvironment: JavaSE-17
Bug 400328 - [visualizer] Make Multicore Visualizer packages internal Change-Id: I09ce5046ccc0935ef036bb6a707900a308f7204f Reviewed-on: https://git.eclipse.org/r/10255 Reviewed-by: William Swanson <traveler@tilera.com> Reviewed-by: Marc Khouzam <marc.khouzam@ericsson.com> IP-Clean: Marc Khouzam <marc.khouzam@ericsson.com> Tested-by: Marc Khouzam <marc.khouzam@ericsson.com>
2013-02-08 10:58:13 -05:00
Export-Package: org.eclipse.cdt.dsf.gdb.multicorevisualizer.internal.ui;x-internal:=true,
org.eclipse.cdt.dsf.gdb.multicorevisualizer.internal.ui.actions;x-internal:=true,
org.eclipse.cdt.dsf.gdb.multicorevisualizer.internal.ui.model;x-internal:=true,
org.eclipse.cdt.dsf.gdb.multicorevisualizer.internal.ui.view;x-internal:=true,
org.eclipse.cdt.dsf.gdb.multicorevisualizer.internal.utils;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.dsf.gdb.multicorevisualizer.ui
Reference in a new issue Copy permalink