Exact

Exact Union RegExp

Jonah Graham 8687aec665 [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 1087dc5f22, 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-19 14:28:08 -04:00
..
org.eclipse.cdt.doc.isv	[releng] Require target platform bundles as minimum version	2025-05-19 14:28:08 -04:00
org.eclipse.cdt.doc.user	[releng] Require target platform bundles as minimum version	2025-05-19 14:28:08 -04:00