mirrors/cdt
1
0
Fork 0
mirror of https://github.com/eclipse-cdt/cdt synced 2025-07-04 07:35:24 +02:00
Code Issues Wiki Activity
cdt/visualizer/org.eclipse.cdt.visualizer.examples/META-INF/MANIFEST.MF

21 lines
965 B
Text
Raw Normal View History

First commit of an example visualizer, which displays a count of problem markers.
2012-02-26 22:28:50 -05:00
Manifest-Version: 1.0
Bundle-ManifestVersion: 2
Bundle-Name: %plugin.name
Bundle-SymbolicName: org.eclipse.cdt.visualizer.examples;singleton:=true
Build with Tycho 4.0.6 (#715) Includes bundle version bumps for new version of ECJ and target platform update. Co-authored-by: Александър Куртаков <akurtakov@gmail.com>
2024-02-22 21:38:57 -05:00
Bundle-Version: 1.0.200.qualifier
First commit of an example visualizer, which displays a count of problem markers.
2012-02-26 22:28:50 -05:00
Bundle-Activator: org.eclipse.cdt.visualizer.examples.VisualizerExamplesPlugin
Bundle-Vendor: %provider.name
[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.core.resources;bundle-version="[3.22.200,4)",
org.eclipse.jface.text;bundle-version="[3.28.0,4)",
org.eclipse.cdt.visualizer.ui;bundle-version="[1.5.400,2)",
org.eclipse.cdt.visualizer.core;bundle-version="[1.2.200,2)"
Update to Java 17 as BREE. Fixes #80
2022-10-01 19:59:59 -04:00
Bundle-RequiredExecutionEnvironment: JavaSE-17
First commit of an example visualizer, which displays a count of problem markers.
2012-02-26 22:28:50 -05:00
Bundle-ActivationPolicy: lazy
Bug 372797: Update based on comments.
2012-03-02 10:47:06 -05:00
Export-Package: org.eclipse.cdt.visualizer.examples,
Missing exports to o.e.cdt.visualizer.examples Signed-off-by: Marc Khouzam <marc.khouzam@ericsson.com>
2014-04-21 16:07:22 -04:00
org.eclipse.cdt.visualizer.examples.problemvisualizer,
org.eclipse.cdt.visualizer.examples.sourcegraph
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.visualizer.examples
Fixed "Key X is not found in localization properties file" warning Change-Id: I467386ce652c67507c9373a669a60dbb8a8f8e2d Signed-off-by: Torbjörn Svensson <azoff@svenskalinuxforeningen.se>
2020-08-28 21:20:14 +02:00
Bundle-Localization: plugin
Reference in a new issue Copy permalink