mirrors/cdt
1
0
Fork 0
mirror of https://github.com/eclipse-cdt/cdt synced 2025-08-28 18:53:20 +02:00
Code Issues Wiki Activity
cdt/codan/org.eclipse.cdt.codan.checkers.ui/META-INF/MANIFEST.MF

26 lines
1.3 KiB
Text
Raw Normal View History

plugin for checkers ui elements
2009-04-18 02:11:07 +00:00
Manifest-Version: 1.0
Bundle-ManifestVersion: 2
Externalized strings in manifest
2010-05-31 01:42:48 +00:00
Bundle-Name: %Bundle-Name
plugin for checkers ui elements
2009-04-18 02:11:07 +00:00
Bundle-SymbolicName: org.eclipse.cdt.codan.checkers.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: 3.4.300.qualifier
[279740] API scrub
2010-03-08 19:51:33 +00:00
Bundle-Activator: org.eclipse.cdt.codan.internal.checkers.ui.CheckersUiActivator
[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.core.resources;bundle-version="[3.22.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.core;bundle-version="[9.1.0,10)",
org.eclipse.cdt.codan.checkers;bundle-version="[3.5.700,4)",
org.eclipse.cdt.codan.core;bundle-version="[4.2.300,5)",
org.eclipse.cdt.codan.core.cxx;bundle-version="[3.6.200,4)",
org.eclipse.cdt.codan.ui.cxx;bundle-version="[3.7.100,4)",
org.eclipse.cdt.ui;bundle-version="[9.0.100,10)",
org.eclipse.jface.text;bundle-version="[3.28.0,4)",
org.eclipse.ltk.core.refactoring;bundle-version="[3.15.0,4)",
org.eclipse.ui;bundle-version="[3.207.200,4)",
org.eclipse.ui.ide;bundle-version="[3.22.600,4)"
plugin for checkers ui elements
2009-04-18 02:11:07 +00:00
Bundle-ActivationPolicy: lazy
Update to Java 17 as BREE. Fixes #80
2022-10-01 19:59:59 -04:00
Bundle-RequiredExecutionEnvironment: JavaSE-17
Externalized strings in manifest
2010-05-31 01:42:48 +00:00
Bundle-Vendor: %Bundle-Vendor
Export-Package: org.eclipse.cdt.codan.internal.checkers.ui;x-internal:=true,
releng: Make use of Tycho POM-less functionality This removes a lot of pom.xml from the source tree. This is using the "POM-less" Tycho functionality. See https://wiki.eclipse.org/Tycho/Release_Notes/0.24#POM-less_Tycho_builds One advantage of this is that you do not need to update the version in the pom.xml when you change it in the MANIFEST.MF because the pom.xml is automatically generated. This also reduces a lot of the duplicated information and pom.xml repetition. - Maven 3.3 and up is required. - Only eclipse-plugins and eclipse-features can be pom-less. Repositories, target and others still have pom.xml. - New parent poms are added because a parent is necessary directly one level above the plug-in/feature that will have its pom generated - Some test plug-ins had to be renamed .test -> .tests because it's required so that it detects that it's a test plug-in - Some suites were renamed so that they all use the same consistent name "AutomatedIntegrationSuite" - Profiles were added for the more common test configurations. They are activated by the presence of simple .properties files that only serve to activate the correct profile. The profiles: - One for UI tests (UI present and start in UI thread) - One for SWTBot tests (UI present and do not start in UI thread) Other test plug-ins that are too different are kept intact and still have a pom.xml - Fragments are kept intact since they all have different target platform configurations Change-Id: I9d73380eb766f547830c552daf08053a30b1845c Signed-off-by: Marc-Andre Laperle <marc-andre.laperle@ericsson.com>
2017-02-06 16:22:23 -05:00
org.eclipse.cdt.codan.internal.checkers.ui.quickfix;x-friends:="org.eclipse.cdt.codan.checkers.ui.tests"
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.codan.checkers.ui
Bug 319196 - quick fixes for adding local variables,etc. based on patch from Tomasz Wesolowski
2010-07-21 02:27:35 +00:00
Reference in a new issue Copy permalink