mirrors/cdt
1
0
Fork 0
mirror of https://github.com/eclipse-cdt/cdt synced 2025-08-09 17:25:38 +02:00
Code Issues Wiki Activity
cdt/unittest/org.eclipse.cdt.unittest/META-INF/MANIFEST.MF

31 lines
1.5 KiB
Text
Raw Normal View History

Bug 569172 - Debug framework should support generic "unit test" view A C/C++ test runner client demonstrating the functionality of Unit Test View bundle. See: https://git.eclipse.org/r/c/platform/eclipse.platform.debug/+/171116 for Unit Test bundle proposal Also-By: Mickael Istria <mistria@redhat.com> Also-By: Alexander Kurtakov <akurtako@redhat.com> Signed-off-by: Victor Rubezhny <vrubezhny@redhat.com> Change-Id: I93bc368549a640906a198e04456d5f9fd87eedb5
2020-11-23 22:41:25 +01:00
Manifest-Version: 1.0
Automatic-Module-Name: org.eclipse.cdt.unittest
Bundle-ManifestVersion: 2
Bundle-Name: %pluginName
Bundle-SymbolicName: org.eclipse.cdt.unittest;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.1.300.qualifier
Bug 569172 - Debug framework should support generic "unit test" view A C/C++ test runner client demonstrating the functionality of Unit Test View bundle. See: https://git.eclipse.org/r/c/platform/eclipse.platform.debug/+/171116 for Unit Test bundle proposal Also-By: Mickael Istria <mistria@redhat.com> Also-By: Alexander Kurtakov <akurtako@redhat.com> Signed-off-by: Victor Rubezhny <vrubezhny@redhat.com> Change-Id: I93bc368549a640906a198e04456d5f9fd87eedb5
2020-11-23 22:41:25 +01:00
Bundle-Activator: org.eclipse.cdt.unittest.CDTUnitTestPlugin
Bundle-ActivationPolicy: lazy
Bundle-Vendor: %providerName
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.unittest.ui;bundle-version="[1.1.600,2)",
org.eclipse.cdt.testsrunner;bundle-version="[8.3.300,9)",
org.eclipse.cdt.debug.core;bundle-version="[9.0.0,10)",
org.eclipse.cdt.debug.ui;bundle-version="[8.5.700,9)",
org.eclipse.cdt.managedbuilder.core;bundle-version="[9.7.100,10)",
org.eclipse.cdt.launch;bundle-version="[11.0.0,12)",
org.eclipse.cdt.dsf.gdb;bundle-version="[7.1.500,8)",
org.eclipse.cdt.dsf.gdb.ui;bundle-version="[2.8.700,3)",
org.eclipse.cdt.core;bundle-version="[9.1.0,10)",
org.eclipse.cdt.ui;bundle-version="[9.0.100,10)",
org.eclipse.search;bundle-version="[3.17.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.0.0)",
[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.ui;bundle-version="[3.207.200,4.0.0)",
org.eclipse.debug.core;bundle-version="[3.23.0,4.0.0)",
org.eclipse.debug.ui;bundle-version="[3.18.800,4.0.0)",
org.eclipse.jface.text;bundle-version="[3.28.0,4.0.0)",
org.eclipse.ui.workbench.texteditor;bundle-version="[3.19.200,4.0.0)",
org.eclipse.core.filesystem;bundle-version="[1.11.200,2)",
org.eclipse.ui.ide;bundle-version="[3.22.600,4.0.0)"
Update to Java 17 as BREE. Fixes #80
2022-10-01 19:59:59 -04:00
Bundle-RequiredExecutionEnvironment: JavaSE-17
Reference in a new issue Copy permalink