When we decided to delay CDT 12.0 by 3 months it also meant that
the desired target was 2024-12, this commit makes this change
across the target platform
- Configure the JRE for Java 21.
- Clone cdt-lsp
- Include its source locator in the targlet
- Configure both clones to rebase new branches by default.
- Add a working set for the CDT LSP projects.
Includes updating to latest target platform. This should
also fix#591 but it is hard to tell until after it is
integrated into SimRel and the output checked in EPP.
Fixes https://github.com/eclipse-cdt/cdt/issues/591
Part of #548
CDT.setup was allowing devs to choose the target platform, but
in reality most choices don't work. Instead force the known
correct value which is what Eclipse Platform does too.
Fixes#571
Includes:
- Sign all artifacts, particularly 3rd party with CDT's PGP key
- Using maven version managed and updated by EF Webmasters
- Update to latest SnakeYAML
- Move some 3rd party dependencies to Import-Package (instead of
Require-Bundle)
Don't install org.eclipse.pde.api.tools.ee.feature.feature.group because
it's no longer in the latest update site, and that causes problems like
this one as noticed by a user:
https://www.eclipse.org/forums/index.php?t=msg&th=1111320&goto=1854139&#msg_1854139
Move all the tasks up to the project level.
Include a * requirement on the CDT targlet so that all projects are
imported by the targlet task with no need for a separate import task.
Probably many of the explicitly listed requirements are no longer needed
because all requirements of all projects in the clone are resolved now
automatically. Also ensure that all platforms are resolved so that all
of CDT fragments are imported.
Move the Git clone task before the modular targlet task so that the
clone is available during the first resolution.
Add an EclipseIni task so that the CDT.setup is redirected into the
local clone's version such that you can modify that setup and test it
locally via Help -> Perform Setup tasks (and so that Navigate -> Open
Setup -> CDT opens the editable workspace version).
https://bugs.eclipse.org/bugs/show_bug.cgi?id=580505
Used info from https://projects.eclipse.org/releases/2022-03 to determine
the versions of components.
Contributed by STMicroelectronics
Change-Id: If6c4ccfc18e87ff91cbed8c6236139c01819f77a
Signed-off-by: Torbjörn Svensson <torbjorn.svensson@st.com>
Use info from https://projects.eclipse.org/releases/2021-12 to determine
the versions of components + M1 build of Eclipse Platform.
Orbit has not done an M1 release.
Change-Id: I1b23daeae7ae280502db5155e4a7bd34b89e7db4
Signed-off-by: Alexander Fedorov <alexander.fedorov@arsysop.ru>
Also-by: Jonah Graham <jonah@kichwacoders.com>
Use eclipse.target.platform.latest
Sync with Target
Change-Id: Ife2508edb72eaa45bfe33618d3cbde47a5d34d6a
Signed-off-by: Alexander Fedorov <alexander.fedorov@arsysop.ru>
Updated Baseline to 2021-09
Updated Target to 2021-09+
Change-Id: I9dd301b2b759452c743238626ac671008e2cd254
Signed-off-by: Alexander Fedorov <alexander.fedorov@arsysop.ru>
This includes requiring older version Hamcrest as the org.hamcrest
bundle was recently update in Orbit to a new major version that
isn't compatible.
Change-Id: I7cb23f0be058d1404b93b1a76cbfe8182a3ded14
The URL we were using was a milestone location - this location is
the release location. The milestone location has since been deleted.
Change-Id: I2e29fbf36d51d17cd53754afc5175275257f0983
Other dependencies, such as platform may be updated later in the
dev cycle to increase CDT's minimum dependency version to the 2021-06
or even later releases.
Change-Id: Ib6386dca74f9e1327f2f7beae0adf13f54e668f3
Updated baseline to 2021-03 for
* cdt-baseline.target
* CDT.setup
* parent pom is not changed
Updated target to 2021-03 where it was pointing to older versions for
* cdt.target
* CDT.setup
Change-Id: Ie8117b4cb6f86c8ad105710d14dde6222380d289
Signed-off-by: Alexander Fedorov <alexander.fedorov@arsysop.ru>
