mirrors/cdt
1
0
Fork 0
mirror of https://github.com/eclipse-cdt/cdt synced 2024-10-28 12:09:40 +01:00
Code Issues Projects Releases Packages Wiki Activity Actions
cdt/pom.xml

1066 lines
36 KiB
XML
Raw Normal View History

Mavenizing CDT releng. Also removed unsupported cdt.core fragments from the platform feature.
2011-06-28 11:21:58 +02:00
<?xml version="1.0" encoding="UTF-8"?>
Bug 551817 - Add missing CONTRIBUTING file to CDT This also includes the minimum legal requirements for basic build instructions (or links to them) Change-Id: Ib95bf44a2ada75069e0a190aaf3d68fccc6f1282
2020-01-16 18:32:21 +01:00
<!--
[#657] CDT cannot be built on Java 21 due to security manager changes * Switch CI to Java 21 * Remove config generation for debug application * Remove `org.eclipse.osgi.services` from `proxy.server` product * Remove `org.eclipse.osgi.services` from `org.eclipse.cdt.debug.application.product` product * Move `org.eclipse.cdt.debug.application.product` from profile to general part Signed-off-by: Alexander Fedorov <alexander.fedorov@arsysop.ru>
2024-04-19 17:21:37 +02:00
Copyright (c) 2011, 2024 Wind River Systems, Inc. and others.
Bug 551817 - Add missing CONTRIBUTING file to CDT This also includes the minimum legal requirements for basic build instructions (or links to them) Change-Id: Ib95bf44a2ada75069e0a190aaf3d68fccc6f1282
2020-01-16 18:32:21 +01:00
This program and the accompanying materials
are made available under the terms of the Eclipse Public License 2.0
which accompanies this distribution, and is available at
https://www.eclipse.org/legal/epl-2.0/
SPDX-License-Identifier: EPL-2.0
-->
Mavenizing CDT releng. Also removed unsupported cdt.core fragments from the platform feature.
2011-06-28 11:21:58 +02:00
<project
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd"
xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<modelVersion>4.0.0</modelVersion>
<groupId>org.eclipse.cdt</groupId>
<artifactId>cdt-parent</artifactId>
Prepare repo for 11.7.0 development (#813)
2024-06-05 19:19:53 +02:00
<version>11.7.0-SNAPSHOT</version>
Mavenizing CDT releng. Also removed unsupported cdt.core fragments from the platform feature.
2011-06-28 11:21:58 +02:00
<packaging>pom</packaging>
<name>CDT Parent</name>
<properties>
Update to Tycho 4.0.1 The error handling in Tycho 4 identifies when bundles are listed in category.xml but not available. The removed bundles were not in the output, and with this change the error is resolved in the build. Updated setting for maven enforcer to match Tycho requirements.
2023-07-22 18:14:06 +02:00
<required-maven-version>3.9.1</required-maven-version>
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-23 03:38:57 +01:00
<tycho-version>4.0.6</tycho-version>
Update CBI plugins to 1.4.3
2024-02-21 11:55:19 +01:00
<cbi-plugins.version>1.4.3</cbi-plugins.version>
Add support for Sonar reporting. Change-Id: Ibd6bf69cb88ae41f0e768d5ac50656589eb00ec0 Reviewed-on: https://git.eclipse.org/r/14717 Reviewed-by: Jeff Johnston <jjohnstn@redhat.com> IP-Clean: Jeff Johnston <jjohnstn@redhat.com> Tested-by: Jeff Johnston <jjohnstn@redhat.com>
2013-07-20 00:54:21 +02:00
<sonar.core.codeCoveragePlugin>jacoco</sonar.core.codeCoveragePlugin>
Bring optional p2 update sites up to date The simrel and cdt update sites can be used to run partial builds and are not used by default when doing builds. This change brings those URLs up to date.
2024-05-10 17:51:50 +02:00
<cdt-site>https://ci.eclipse.org/cdt/job/cdt/job/main/lastSuccessfulBuild/artifact/releng/org.eclipse.cdt.repo/target/repository</cdt-site>
<simrel-site>https://download.eclipse.org/staging/2024-06/</simrel-site>
Revert "Point cdt_8_7 build to its own location" This reverts commit 4714a3bf5942b93300bc8d1f442a9e34e3f7f223.
2015-05-11 21:57:08 +02:00
<repo-path>tools/cdt/builds/master/nightly</repo-path>
Add support for Sonar reporting. Change-Id: Ibd6bf69cb88ae41f0e768d5ac50656589eb00ec0 Reviewed-on: https://git.eclipse.org/r/14717 Reviewed-by: Jeff Johnston <jjohnstn@redhat.com> IP-Clean: Jeff Johnston <jjohnstn@redhat.com> Tested-by: Jeff Johnston <jjohnstn@redhat.com>
2013-07-20 00:54:21 +02:00
<sonar.dynamicAnalysis>reuseReports</sonar.dynamicAnalysis>
<sonar.jacoco.reportPath>${project.basedir}/../../target/jacoco.exec</sonar.jacoco.reportPath>
Bug 562494: Update BREE to Java 11 Change-Id: I0c91aafc0cb1b179936acbd4c9df2d961899e3fa
2020-08-23 14:05:03 +02:00
<sonar.java.source>11</sonar.java.source>
Clean-up and use a single target file Old targets were not working anymore. Also, rename the 4.6 target to just cdt.target because there is only one that is primarily used. This should be less confusing to new-comers. Change-Id: Iaa45fbc5d91cfb47e7e60e549469e74dc5ffe369 Signed-off-by: Marc-Andre Laperle <marc-andre.laperle@ericsson.com>
2016-01-07 00:45:29 +01:00
<target-platform>cdt</target-platform>
[releng] Bump version number of docs plug-ins These docs plug-ins were having baselinereplace-p2-metadata. This is due to still having problems with the compare&replace logic. The root pom.xml lits <pattern>index/*</pattern> to exclude from compare, which means if the only thing that changes is the generate files, and not the source files, then the jar is a candidate for replace. In commit 3bab315fd23, the version of help-docs-eclipserun-repo was changed, which means that the generated output changes too. Change-Id: I7f73159776d209aadaa70587988652e125b60851
2019-09-09 21:23:53 +02:00
[releng] Update help-docs-eclipserun-repo in root pom.xml and: - bump versions of all the docs plug-ins. - improve comment so that next person can do it more easily - change to using https in the URL Change-Id: I62bd970f03e1ce081d4655ddbf6c742be2623acd
2021-12-14 17:17:55 +01:00
<!-- When changing this value, consider also bumping the version numbers of all the docs plug-ins (those with build-doc profile in pom.xml)
so that compare&replace does not replace the the newly built docs because the only change is in the filtered out index/* resources. -->
Prepare repo for CDT 11.4.0 development Part of #548
2023-09-14 22:46:13 +02:00
<help-docs-eclipserun-repo>https://download.eclipse.org/eclipse/updates/4.29/R-4.29-202309031000/</help-docs-eclipserun-repo>
[releng] Bump version number of docs plug-ins These docs plug-ins were having baselinereplace-p2-metadata. This is due to still having problems with the compare&replace logic. The root pom.xml lits <pattern>index/*</pattern> to exclude from compare, which means if the only thing that changes is the generate files, and not the source files, then the jar is a candidate for replace. In commit 3bab315fd23, the version of help-docs-eclipserun-repo was changed, which means that the generated output changes too. Change-Id: I7f73159776d209aadaa70587988652e125b60851
2019-09-09 21:23:53 +02:00
Update references of git.eclipse.org to github
2022-08-22 23:31:58 +02:00
<tycho.scmUrl>scm:git:https://github.com/eclipse-cdt/cdt</tycho.scmUrl>
Add reflection access when running some old tests (#28) This is the exception that would have been raised. java.lang.reflect.UndeclaredThrowableException at org.eclipse.cdt.core.cdescriptor.tests.CDescriptorOldTests.testProjectDataCreate(CDescriptorOldTests.java:370) Caused by: java.lang.IllegalAccessException: class org.eclipse.cdt.internal.core.CConfigBasedDescriptor$1 cannot access class com.sun.org.apache.xerces.internal.dom.ParentNode (in module java.xml) because module java.xml does not export com.sun.org.apache.xerces.internal.dom to unnamed module @772861aa at org.eclipse.cdt.core.cdescriptor.tests.CDescriptorOldTests.testProjectDataCreate(CDescriptorOldTests.java:370) It may be that --add-opens=java.xml/com.sun.org.apache.xerces.internal.dom=ALL-UNNAMED can/should be added to the product, similar to linuxtools in https://github.com/eclipse-linuxtools/org.eclipse.linuxtools/pull/20/files but as this affects only some special use cases that are probably not really in existence anymore we are just fixing the tests. Alternative would be to simply delete these old tests (CDescriptorOldTests) and surrounding code.
2022-08-10 21:31:54 +02:00
<!-- Some old tests, like CDescriptorOldTests, fail due to reflection access. Therefore we add-opens to make that pass -->
<base.test.vmargs>-Xms256m -Xmx512m -ea --add-opens=java.xml/com.sun.org.apache.xerces.internal.dom=ALL-UNNAMED</base.test.vmargs>
Prepare repo for 11.7.0 development (#813)
2024-06-05 19:19:53 +02:00
<comparator.repo>https://download.eclipse.org/tools/cdt/builds/11.6/cdt-11.6.0-rc2/</comparator.repo>
<api-baseline.repo>https://download.eclipse.org/tools/cdt/builds/11.6/cdt-11.6.0-rc2/</api-baseline.repo>
<api-baseline.repo.simrel>https://download.eclipse.org/releases/2024-06/</api-baseline.repo.simrel>
[releng] Change default to be baseline compare and replace is not run Use baseline-compare-and-replace profile to run it. Change-Id: Iaacfad8f920f28cf773763e804be90ba8c5f30cf
2019-07-03 19:56:07 +02:00
<!-- these parameters are to control baseline replace and compare. On a local build you want
Bug 547894: Provide a way to skip baseline replace and compare Change-Id: If8080db7374eabb7a640deba0fab1e26a785ac5c
2019-06-26 15:56:49 +02:00
to avoid baseline replace and compare, especially if you have different versions of Java than
[releng] Change default to be baseline compare and replace is not run Use baseline-compare-and-replace profile to run it. Change-Id: Iaacfad8f920f28cf773763e804be90ba8c5f30cf
2019-07-03 19:56:07 +02:00
the baseline was built with. This is the default.
Bug 547894: Provide a way to skip baseline replace and compare Change-Id: If8080db7374eabb7a640deba0fab1e26a785ac5c
2019-06-26 15:56:49 +02:00
[releng] Change default to be baseline compare and replace is not run Use baseline-compare-and-replace profile to run it. Change-Id: Iaacfad8f920f28cf773763e804be90ba8c5f30cf
2019-07-03 19:56:07 +02:00
If you have the same version of Java as the build machine you can run baseline comparison and
replace. To do that run with the baseline-compare-and-replace profile.
Bug 547894: Provide a way to skip baseline replace and compare Change-Id: If8080db7374eabb7a640deba0fab1e26a785ac5c
2019-06-26 15:56:49 +02:00
-->
[releng] Change default to be baseline compare and replace is not run Use baseline-compare-and-replace profile to run it. Change-Id: Iaacfad8f920f28cf773763e804be90ba8c5f30cf
2019-07-03 19:56:07 +02:00
<compare-version-with-baselines.skip>true</compare-version-with-baselines.skip>
<replace-version-with-baselines.mode>disable</replace-version-with-baselines.mode>
<replace-version-with-baselines.replace>none</replace-version-with-baselines.replace>
Bug 540367 - Enable Reproducible Version Qualifiers Change-Id: I1ccd2330951a83a7632c67a6274b7527cd9f237c
2018-10-22 16:09:31 +02:00
<!--
Valid options: error, warning, and ignore
jgit.dirtyWorkingTree checking was added as of Tycho 0.19.0
see: https://bugs.eclipse.org/419030
-->
<jgit.dirtyWorkingTree-cdtDefault>error</jgit.dirtyWorkingTree-cdtDefault>
Bug 515304: profiles to parallelize testsuite Change-Id: I02095334c2176bfb9a2968d91b6175af37123f5b Signed-off-by: Jonah Graham <jonah@kichwacoders.com>
2017-04-15 01:14:38 +02:00
<!-- By default cdt-other.skip.tests will be false as none of
the skip-tests profiles will be activated. When one is
activated, this allows us to skip all other cdt tests not
explicitly skipped further down the pom hierarchy.
Recall that the command line will take precedence, so
-DskipTests will override anything else as normal maven
users expect. -->
<skipTests>${cdt-other.skip.tests}</skipTests>
DSF-GDB tests in GitHub Actions - Fix the running so that the correct gdb is used. - Only run DSF tests if dsf directories have been modified - Default to using gdb,gdbserver on the PATH when running tests - Remove double reporting of test results
2022-10-10 00:09:47 +02:00
<dsf.gdb.tests.gdbPath></dsf.gdb.tests.gdbPath>
<cdt.tests.dsf.gdb.versions></cdt.tests.dsf.gdb.versions>
Bug 558827: Add build id timestamp to features properly This was lost when the build system was moved to Maven/Tycho for CDT 8 and restores the information. Note that with the p2 baseline compare and replace this will show the build id of when the branding plugin (the one with the about.mappings) was built, which compared to the feature version may be older. The about.mappings, as it is generated on each build, is ignored from p2 compare and replace. Change-Id: I38d1fcc5f618d4037baa2c8b908952421c712fc6
2020-01-06 18:03:23 +01:00
<maven.build.timestamp.format>yyyyMMdd-HHmm</maven.build.timestamp.format>
<buildTimestamp>${maven.build.timestamp}</buildTimestamp>
<buildId>${buildTimestamp}</buildId>
Mavenizing CDT releng. Also removed unsupported cdt.core fragments from the platform feature.
2011-06-28 11:21:58 +02:00
</properties>
<licenses>
<license>
Bug 540371: Update to EPLv2 using releng/scripts/change_to_eplv2.sh Change-Id: Ifbb1d5af2a00bd5634dea200320e8c4303ffca6c
2018-11-20 14:02:15 +01:00
<name>Eclipse Public License 2.0</name>
Mavenizing CDT releng. Also removed unsupported cdt.core fragments from the platform feature.
2011-06-28 11:21:58 +02:00
<comments>
Clean up Maven build (#662) * remove invalid tycho resolver config (not valid since many versions) * fix PMD plugin configuration (config attribute was renamed in 3.18) * remove duplicate versions already managed in pluginManagement section * fix indentation * move all not yet configured versions into pluginManagement of the parent module to avoid further duplication * consume the target platform as file, not as maven artifact (this simplifies building a single module A LOT) * remove invalid tycho-source-plugin configuration * disable tycho consumer POM generation (not needed here, and avoids a warning in each module) * remove prerequisites. that's for maven plugins only, and this POM already contains the better suited similar maven enforcer rule * enforce UTF-8 for javadoc generation (the build fails on Windows otherwise, trying to read some Japanese? characters with the Windows default encoding)
2023-12-28 20:35:58 +01:00
Mavenizing CDT releng. Also removed unsupported cdt.core fragments from the platform feature.
2011-06-28 11:21:58 +02:00
This program and the accompanying materials are made
Bug 540371: Update to EPLv2 using releng/scripts/change_to_eplv2.sh Change-Id: Ifbb1d5af2a00bd5634dea200320e8c4303ffca6c
2018-11-20 14:02:15 +01:00
available under the terms of the Eclipse Public License 2.0
Mavenizing CDT releng. Also removed unsupported cdt.core fragments from the platform feature.
2011-06-28 11:21:58 +02:00
which accompanies this distribution, and is available at
Bug 540371: Update to EPLv2 using releng/scripts/change_to_eplv2.sh Change-Id: Ifbb1d5af2a00bd5634dea200320e8c4303ffca6c
2018-11-20 14:02:15 +01:00
https://www.eclipse.org/legal/epl-2.0/
Clean up Maven build (#662) * remove invalid tycho resolver config (not valid since many versions) * fix PMD plugin configuration (config attribute was renamed in 3.18) * remove duplicate versions already managed in pluginManagement section * fix indentation * move all not yet configured versions into pluginManagement of the parent module to avoid further duplication * consume the target platform as file, not as maven artifact (this simplifies building a single module A LOT) * remove invalid tycho-source-plugin configuration * disable tycho consumer POM generation (not needed here, and avoids a warning in each module) * remove prerequisites. that's for maven plugins only, and this POM already contains the better suited similar maven enforcer rule * enforce UTF-8 for javadoc generation (the build fails on Windows otherwise, trying to read some Japanese? characters with the Windows default encoding)
2023-12-28 20:35:58 +01:00
Bug 540371: Update to EPLv2 using releng/scripts/change_to_eplv2.sh Change-Id: Ifbb1d5af2a00bd5634dea200320e8c4303ffca6c
2018-11-20 14:02:15 +01:00
SPDX-License-Identifier: EPL-2.0
Mavenizing CDT releng. Also removed unsupported cdt.core fragments from the platform feature.
2011-06-28 11:21:58 +02:00
</comments>
</license>
</licenses>
<modules>
Add UI tests plugin for CMake. Fix a couple of bugs it found. Also restructures the pom.xmls to put the modules in the top level so we can order them to have the test plugins build after them. Change-Id: I2f0e4ebd252791fb8844cdf0f635d574946207aa
2017-10-05 02:47:32 +02:00
<!-- The test plug-ins need to be at the end -->
<module>build/org.eclipse.cdt.build.gcc.core</module>
Add the core build gcc ui plugin to the gcc build feature. Change-Id: I309bf8c785107ad8edd68664d175c7e94a900ea4
2017-11-05 03:26:18 +01:00
<module>build/org.eclipse.cdt.build.gcc.ui</module>
Add UI tests plugin for CMake. Fix a couple of bugs it found. Also restructures the pom.xmls to put the modules in the top level so we can order them to have the test plugins build after them. Change-Id: I2f0e4ebd252791fb8844cdf0f635d574946207aa
2017-10-05 02:47:32 +02:00
<module>build/org.eclipse.cdt.make.core</module>
<module>build/org.eclipse.cdt.make.ui</module>
<module>build/org.eclipse.cdt.managedbuilder.core</module>
<module>build/org.eclipse.cdt.managedbuilder.ui</module>
<module>build/org.eclipse.cdt.managedbuilder.gnu.ui</module>
Bug 571566: Document how to choose workspace for headless build Moved handling of "-help" to a new plugin using the same approach as was used for the JavaCodeFormatter in bug 543363. This mainly allows to get the help text even if the workspace is missing. Contributed by STMicroelectronics Change-Id: I4ee2e93f0e8fed13ddebd70c3bce58f047aa1d12 Also-by: Jonah Graham <jonah@kichwacoders.com> Signed-off-by: Torbjörn SVENSSON <torbjorn.svensson@st.com>
2021-02-26 20:22:50 +01:00
<module>build/org.eclipse.cdt.managedbuilder.headlessbuilderapp</module>
Add UI tests plugin for CMake. Fix a couple of bugs it found. Also restructures the pom.xmls to put the modules in the top level so we can order them to have the test plugins build after them. Change-Id: I2f0e4ebd252791fb8844cdf0f635d574946207aa
2017-10-05 02:47:32 +02:00
<module>build/org.eclipse.cdt.gnu.build-feature</module>
<module>build/org.eclipse.cdt.autotools.core</module>
<module>build/org.eclipse.cdt.autotools.docs</module>
<module>build/org.eclipse.cdt.autotools.ui</module>
<module>build/org.eclipse.cdt.autotools-feature</module>
Bug 530000 - Add Meson Build support - initial contribution of Meson Build support based upon Core Build CMake Change-Id: I9a91901254b7750f4f5eef69ed5375a5c1cce0a4
2018-01-30 21:46:07 +01:00
<module>build/org.eclipse.cdt.meson.core</module>
Add Meson docs plug-in Change-Id: I9153edd6f2708de475855ca3dbdb6323432e37ac
2018-03-06 23:16:48 +01:00
<module>build/org.eclipse.cdt.meson.docs</module>
Bug 530000 - Add Meson Build support - initial contribution of Meson Build support based upon Core Build CMake Change-Id: I9a91901254b7750f4f5eef69ed5375a5c1cce0a4
2018-01-30 21:46:07 +01:00
<module>build/org.eclipse.cdt.meson.ui</module>
Bug 530000 - Add Meson Build support Editors for meson.build, meson_options.txt and *.ninja files. Just highlighting for now based on textmate grammars. Added tm4e to target to enable resolving tm4e bundles. Change-Id: I22859b2d39a96dcd777ee96d2a5e7465e4884839 Signed-off-by: Alexander Kurtakov <akurtako@redhat.com>
2018-02-09 18:45:01 +01:00
<module>build/org.eclipse.cdt.meson.ui.editor</module>
Bug 530000 - Add Meson Build support - initial contribution of Meson Build support based upon Core Build CMake Change-Id: I9a91901254b7750f4f5eef69ed5375a5c1cce0a4
2018-01-30 21:46:07 +01:00
<module>build/org.eclipse.cdt.meson-feature</module>
Bug 525591: autotools: Initial core build implementation Add core, UI and feature plugins for the new autotools project which uses template wizard and core build. The template wizard currently supports generating a simple autotools project as described using a template manifest. The project generator sets new autotools nature associated with new autotools build config provider. The generated autotools project has been tested to compile fine with gcc (x86_64-linux-gnu-gcc) toolchain. Change-Id: I8349999d551bb693725a246340cf46266150fadc Signed-off-by: Chin Huat Ang <chin.huat.ang@intel.com>
2017-10-23 20:16:05 +02:00
<module>build/org.eclipse.cdt.core.autotools.core</module>
<module>build/org.eclipse.cdt.core.autotools.ui</module>
<module>build/org.eclipse.cdt.core.autotools-feature</module>
Add UI tests plugin for CMake. Fix a couple of bugs it found. Also restructures the pom.xmls to put the modules in the top level so we can order them to have the test plugins build after them. Change-Id: I2f0e4ebd252791fb8844cdf0f635d574946207aa
2017-10-05 02:47:32 +02:00
<module>codan/org.eclipse.cdt.codan.core</module>
<module>codan/org.eclipse.cdt.codan.ui</module>
<module>codan/org.eclipse.cdt.codan.core.cxx</module>
<module>codan/org.eclipse.cdt.codan.ui.cxx</module>
<module>codan/org.eclipse.cdt.codan.checkers</module>
<module>codan/org.eclipse.cdt.codan.checkers.ui</module>
<module>core/org.eclipse.cdt.core.native</module>
<module>core/org.eclipse.cdt.core.linux</module>
<module>core/org.eclipse.cdt.core.linux.x86_64</module>
Bug 565836: Add linux aarch64 for natives Note: the Windows dll is not actually modified, apart from the embedded date stamp to match the date of the jni/ modification Also-by: Liviu Ionescu <ilg@livius.net> Change-Id: Ice3d5e7ae5999a0e4d1866e76e515a91e30e9f11
2020-08-07 02:59:35 +02:00
<module>core/org.eclipse.cdt.core.linux.aarch64</module>
Add UI tests plugin for CMake. Fix a couple of bugs it found. Also restructures the pom.xmls to put the modules in the top level so we can order them to have the test plugins build after them. Change-Id: I2f0e4ebd252791fb8844cdf0f635d574946207aa
2017-10-05 02:47:32 +02:00
<module>core/org.eclipse.cdt.core.linux.ppc64le</module>
<module>core/org.eclipse.cdt.core.win32</module>
<module>core/org.eclipse.cdt.core.win32.x86_64</module>
<module>core/org.eclipse.cdt.core.macosx</module>
<module>core/org.eclipse.cdt.core</module>
<module>core/org.eclipse.cdt.ui</module>
Clean up Maven build (#662) * remove invalid tycho resolver config (not valid since many versions) * fix PMD plugin configuration (config attribute was renamed in 3.18) * remove duplicate versions already managed in pluginManagement section * fix indentation * move all not yet configured versions into pluginManagement of the parent module to avoid further duplication * consume the target platform as file, not as maven artifact (this simplifies building a single module A LOT) * remove invalid tycho-source-plugin configuration * disable tycho consumer POM generation (not needed here, and avoids a warning in each module) * remove prerequisites. that's for maven plugins only, and this POM already contains the better suited similar maven enforcer rule * enforce UTF-8 for javadoc generation (the build fails on Windows otherwise, trying to read some Japanese? characters with the Windows default encoding)
2023-12-28 20:35:58 +01:00
Add UI tests plugin for CMake. Fix a couple of bugs it found. Also restructures the pom.xmls to put the modules in the top level so we can order them to have the test plugins build after them. Change-Id: I2f0e4ebd252791fb8844cdf0f635d574946207aa
2017-10-05 02:47:32 +02:00
<module>cross/org.eclipse.cdt.build.crossgcc</module>
<module>cross/org.eclipse.cdt.build.crossgcc-feature</module>
<module>cross/org.eclipse.cdt.launch.remote</module>
<module>cross/org.eclipse.cdt.launch.remote-feature</module>
Serial Flash Target and Launch. Clean up Generic Launch. Adds target, launch classes, and launch bar support for targets intended to upload their code to flash using a Serial Port. The port is co-ordinated with the Serial Terminal so that the terminal is paused during the upload. Also cleaned up the Generic Launch so it's not using the External Tools launch which has a number of UX issues. This simplifies the settings and gives us more control. And it's made reusable for the Serial Flash launch. Change-Id: I31e9970243fbf1cf22d027bbdb892fde104dbefe
2017-11-13 21:25:52 +01:00
<module>cross/org.eclipse.cdt.launch.serial.core</module>
<module>cross/org.eclipse.cdt.launch.serial.ui</module>
<module>cross/org.eclipse.cdt.launch.serial-feature</module>
Add UI tests plugin for CMake. Fix a couple of bugs it found. Also restructures the pom.xmls to put the modules in the top level so we can order them to have the test plugins build after them. Change-Id: I2f0e4ebd252791fb8844cdf0f635d574946207aa
2017-10-05 02:47:32 +02:00
<module>debug/org.eclipse.cdt.debug.core</module>
<module>debug/org.eclipse.cdt.debug.ui</module>
<module>debug/org.eclipse.cdt.gdb</module>
<module>debug/org.eclipse.cdt.gdb.ui</module>
<module>debug/org.eclipse.cdt.gdb-feature</module>
<module>debug/org.eclipse.cdt.gnu.debug-feature</module>
<module>debug/org.eclipse.cdt.debug.application</module>
<module>debug/org.eclipse.cdt.debug.standalone-feature</module>
[#657] CDT cannot be built on Java 21 due to security manager changes * Switch CI to Java 21 * Remove config generation for debug application * Remove `org.eclipse.osgi.services` from `proxy.server` product * Remove `org.eclipse.osgi.services` from `org.eclipse.cdt.debug.application.product` product * Move `org.eclipse.cdt.debug.application.product` from profile to general part Signed-off-by: Alexander Fedorov <alexander.fedorov@arsysop.ru>
2024-04-19 17:21:37 +02:00
<module>debug/org.eclipse.cdt.debug.application.product</module>
Bug 303083 - Rename spawner bundle to 'native' Native more accurately reflects what we've put there. They're native utilities that can be reused by other Eclipse bundles to access native services. Also fixed up the cdt 4.4 target which had fixed version numbers for some of the dependencies and used RSE out of the Luna repo instead of their latest milestones. Change-Id: I259aa9e92212409378679a8c61bf2fffd05c67a2 Reviewed-on: https://git.eclipse.org/r/27304 Tested-by: Hudson CI Reviewed-by: Doug Schaefer <dschaefer@qnx.com>
2014-05-26 19:29:28 +02:00
Mavenizing CDT releng. Also removed unsupported cdt.core fragments from the platform feature.
2011-06-28 11:21:58 +02:00
<module>doc/org.eclipse.cdt.doc.user</module>
<module>doc/org.eclipse.cdt.doc.isv</module>
Clean up Maven build (#662) * remove invalid tycho resolver config (not valid since many versions) * fix PMD plugin configuration (config attribute was renamed in 3.18) * remove duplicate versions already managed in pluginManagement section * fix indentation * move all not yet configured versions into pluginManagement of the parent module to avoid further duplication * consume the target platform as file, not as maven artifact (this simplifies building a single module A LOT) * remove invalid tycho-source-plugin configuration * disable tycho consumer POM generation (not needed here, and avoids a warning in each module) * remove prerequisites. that's for maven plugins only, and this POM already contains the better suited similar maven enforcer rule * enforce UTF-8 for javadoc generation (the build fails on Windows otherwise, trying to read some Japanese? characters with the Windows default encoding)
2023-12-28 20:35:58 +01:00
Add UI tests plugin for CMake. Fix a couple of bugs it found. Also restructures the pom.xmls to put the modules in the top level so we can order them to have the test plugins build after them. Change-Id: I2f0e4ebd252791fb8844cdf0f635d574946207aa
2017-10-05 02:47:32 +02:00
<module>dsf/org.eclipse.cdt.dsf</module>
<module>dsf/org.eclipse.cdt.dsf.ui</module>
<module>dsf/org.eclipse.cdt.examples.dsf</module>
<module>dsf/org.eclipse.cdt.examples.dsf.pda</module>
<module>dsf/org.eclipse.cdt.examples.dsf.pda.ui</module>
<module>dsf/org.eclipse.cdt.examples.dsf-feature</module>
<module>dsf-gdb/org.eclipse.cdt.dsf.gdb</module>
<module>dsf-gdb/org.eclipse.cdt.dsf.gdb.ui</module>
<module>dsf-gdb/org.eclipse.cdt.dsf.gdb.multicorevisualizer.ui</module>
<module>dsf-gdb/org.eclipse.cdt.gnu.dsf-feature</module>
<module>dsf-gdb/org.eclipse.cdt.gnu.multicorevisualizer-feature</module>
<module>dsf-gdb/org.eclipse.cdt.examples.dsf.gdb</module>
<module>jtag/org.eclipse.cdt.debug.gdbjtag</module>
<module>jtag/org.eclipse.cdt.debug.gdbjtag.core</module>
<module>jtag/org.eclipse.cdt.debug.gdbjtag.ui</module>
<module>jtag/org.eclipse.cdt.debug.gdbjtag-feature</module>
<module>launch/org.eclipse.cdt.launch</module>
Bug 558284 - re-enable docker plug-in Reverts commit d70af1889702ce8621d5c8dc135fe7a3c666f20b. The API change was reverted See https://git.eclipse.org/r/#/c/163943/ Change-Id: If8049308e8f2aec3a1930433af9c6348d641b0ab Signed-off-by: Tony Homer <tony.homer@intel.com>
2020-06-01 07:42:23 +02:00
<module>launch/org.eclipse.cdt.docker.launcher</module>
<module>launch/org.eclipse.cdt.docker.launcher-feature</module>
Bug 565142 - Support using CDT in Eclipse flatpak - modify ProcessFactory to prefix commands with flatpak-spawn when running under Eclipse flatpak - add new FlatpakLaunch class to dsf.gdb to do a prelaunch of gdbserver and set up remote port settings when debugging local C/C++ application under Eclipse flatpak - add new tab to gdb when running under Eclipse flatpak to allow user to specify gdbserver and port number - add new org.eclipse.cdt.flatpak.launcher plug-in which contains a FlatpakCommandLauncherFactory to handle copying header files from host to workspace when developing under Eclipse flatpak - add new FlatpakCommandLauncher class which simply extends CommandLauncher and can be used for debugging purposes to distinguish from regular command launcher - also add new FlatpakHeaderPreferencePage to allow C/C++ users to delete copied headers if needed - dynamically add the headers preference page from FlatpakCommandLaunchFactory if running under Eclipse flatpak - add new ICommandLaunchFactory3 to add an interface to check if headers have been modified/removed and scanner info refresh is required - add new org.eclipse.cdt.flatpak.launcher-feature - give higher priority to ContainerCommandLauncherFactory so if running on Eclipse flatpak, the flatpak factory won't be chosen if both apply (i.e. building in a container but running on Eclipse flatpak) Change-Id: Id68e60c4dd37c4494af10440231ac7b7bbec8d17
2020-08-13 23:30:18 +02:00
<module>launch/org.eclipse.cdt.flatpak.launcher</module>
<module>launch/org.eclipse.cdt.flatpak.launcher-feature</module>
Add UI tests plugin for CMake. Fix a couple of bugs it found. Also restructures the pom.xmls to put the modules in the top level so we can order them to have the test plugins build after them. Change-Id: I2f0e4ebd252791fb8844cdf0f635d574946207aa
2017-10-05 02:47:32 +02:00
<module>llvm/org.eclipse.cdt.managedbuilder.llvm.ui</module>
<module>llvm/org.eclipse.cdt.managedbuilder.llvm-feature</module>
<module>llvm/org.eclipse.cdt.llvm.dsf.lldb.core</module>
<module>llvm/org.eclipse.cdt.llvm.dsf.lldb.ui</module>
<module>llvm/org.eclipse.cdt.llvm.dsf.lldb-feature</module>
Bug 562247 - Add CDT Debug Core Memory bundle Added "org.eclipse.cdt.debug.core.memory" bundle with a stub abstract class to be improved in the future commits Change-Id: I14136379d8e595b7af36084cff8711d1d50a0a28 Signed-off-by: Alexander Fedorov <alexander.fedorov@arsysop.ru>
2020-04-17 10:27:00 +02:00
<module>memory/org.eclipse.cdt.debug.core.memory</module>
Add UI tests plugin for CMake. Fix a couple of bugs it found. Also restructures the pom.xmls to put the modules in the top level so we can order them to have the test plugins build after them. Change-Id: I2f0e4ebd252791fb8844cdf0f635d574946207aa
2017-10-05 02:47:32 +02:00
<module>memory/org.eclipse.cdt.debug.ui.memory.memorybrowser</module>
<module>memory/org.eclipse.cdt.debug.ui.memory.floatingpoint</module>
<module>memory/org.eclipse.cdt.debug.ui.memory.search</module>
<module>memory/org.eclipse.cdt.debug.ui.memory.traditional</module>
<module>memory/org.eclipse.cdt.debug.ui.memory.transport</module>
<module>memory/org.eclipse.cdt.debug.ui.memory-feature</module>
<module>native/org.eclipse.cdt.native.serial</module>
<module>remote/org.eclipse.cdt.remote.core</module>
<module>testsrunner/org.eclipse.cdt.testsrunner</module>
<module>testsrunner/org.eclipse.cdt.testsrunner.boost</module>
<module>testsrunner/org.eclipse.cdt.testsrunner.gtest</module>
<module>testsrunner/org.eclipse.cdt.testsrunner.qttest</module>
<module>testsrunner/org.eclipse.cdt.testsrunner.tap</module>
<module>testsrunner/org.eclipse.cdt.testsrunner.feature</module>
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
<module>unittest/org.eclipse.cdt.unittest</module>
<module>unittest/org.eclipse.cdt.unittest.feature</module>
Bug 559674: Enable CMake plug-ins in build Change-Id: I7950f5679956ad4e763fb4e0d6057e506cf6e948
2020-05-30 02:04:37 +02:00
Add UI tests plugin for CMake. Fix a couple of bugs it found. Also restructures the pom.xmls to put the modules in the top level so we can order them to have the test plugins build after them. Change-Id: I2f0e4ebd252791fb8844cdf0f635d574946207aa
2017-10-05 02:47:32 +02:00
<module>util/org.eclipse.cdt.util</module>
<module>visualizer/org.eclipse.cdt.visualizer.core</module>
<module>visualizer/org.eclipse.cdt.visualizer.examples</module>
<module>visualizer/org.eclipse.cdt.visualizer.ui</module>
<module>visualizer/org.eclipse.cdt.visualizer-feature</module>
<module>windows/org.eclipse.cdt.msw.build</module>
Bug 547967 - MSVC Build Output parser This new Language Settings Provider allows parsing MSVC (cl.exe) compilation commands, It is done similarly to the GCC Build Output Parser. It is not enabled by default but can be enabled when in the context of building with an external builder. In general, MSVC support still needs some work but this output parser greatly facilitates setup for certain types of projects. Change-Id: I3fb110ecdfbac1cabbc16239ad6667a5e628d443 Signed-off-by: Marc-Andre Laperle <malaperle@gmail.com>
2019-06-24 04:43:05 +02:00
<module>windows/org.eclipse.cdt.msw.build.tests</module>
Add UI tests plugin for CMake. Fix a couple of bugs it found. Also restructures the pom.xmls to put the modules in the top level so we can order them to have the test plugins build after them. Change-Id: I2f0e4ebd252791fb8844cdf0f635d574946207aa
2017-10-05 02:47:32 +02:00
<module>windows/org.eclipse.cdt.msw-feature</module>
Bug 558439: Integrate releng for launchbar and tools.templates Change-Id: I63530b50729e79e65e5001b71678348c3a7256ba
2020-01-13 20:09:34 +01:00
<module>launchbar/org.eclipse.launchbar</module>
<module>launchbar/org.eclipse.launchbar.core</module>
<module>launchbar/org.eclipse.launchbar.core.tests</module>
<module>launchbar/org.eclipse.launchbar.remote</module>
<module>launchbar/org.eclipse.launchbar.remote.core</module>
<module>launchbar/org.eclipse.launchbar.remote.ui</module>
<module>launchbar/org.eclipse.launchbar.ui</module>
<module>launchbar/org.eclipse.launchbar.ui.controls</module>
<module>launchbar/org.eclipse.launchbar.ui.tests</module>
<module>tools.templates/org.eclipse.tools.templates.core</module>
<module>tools.templates/org.eclipse.tools.templates.freemarker</module>
<module>tools.templates/org.eclipse.tools.templates.ui</module>
Bug 577097: Integrate o.e.remote releng into CDT Change-Id: I55fbfcfae1c414ae21807473f4ab290db40b5238
2021-12-14 20:33:36 +01:00
<!-- Remote bundles -->
<module>remote/org.eclipse.remote.core</module>
<module>remote/org.eclipse.remote.jsch.core</module>
<module>remote/org.eclipse.remote.jsch.ui</module>
<module>remote/org.eclipse.remote.ui</module>
<!-- Proxy bundles -->
<module>remote/org.eclipse.remote.proxy.core</module>
<module>remote/org.eclipse.remote.proxy.ui</module>
<module>remote/org.eclipse.remote.proxy.protocol.core</module>
<module>remote/org.eclipse.remote.proxy.server.core</module>
<module>remote/org.eclipse.remote.proxy.server.product</module>
<module>remote/org.eclipse.remote.proxy.server.linux.x86_64</module>
<module>remote/org.eclipse.remote.proxy.server.linux.ppc64le</module>
<module>remote/org.eclipse.remote.proxy.server.macosx.x86_64</module>
<!-- Main feature -->
<module>remote/org.eclipse.remote-feature</module>
<!-- Proxy feature -->
<module>remote/org.eclipse.remote.proxy-feature</module>
<!-- Console Terminal feature -->
<module>remote/org.eclipse.remote.console</module>
<module>remote/org.eclipse.remote.console-feature</module>
<!-- Serial Port feature -->
<module>remote/org.eclipse.remote.serial.core</module>
<module>remote/org.eclipse.remote.serial.ui</module>
<module>remote/org.eclipse.remote.serial-feature</module>
<!-- Telnet feature -->
<module>remote/org.eclipse.remote.telnet.core</module>
<module>remote/org.eclipse.remote.telnet.ui</module>
<module>remote/org.eclipse.remote.telnet-feature</module>
<!-- Documentation -->
<module>remote/org.eclipse.remote.doc.isv</module>
Bug 559474: Integrate tm.terminal into CDT's releng Change-Id: I46db42560ec0b93bb265f45920d78c97a32338c3
2020-01-31 16:29:05 +01:00
<module>terminal</module>
Bug 564349 - move code to parse compile_commands.json to subdir jsoncdb Change-Id: I68f3b861b4326adf6da4f9d074a314628c7e8fef Signed-off-by: Martin Weber <fifteenknots505@gmail.com>
2021-07-26 23:00:59 +02:00
<module>jsoncdb</module>
Bug 559674: Enable CMake plug-ins in build Change-Id: I7950f5679956ad4e763fb4e0d6057e506cf6e948
2020-05-30 02:04:37 +02:00
<module>cmake</module>
Add UI tests plugin for CMake. Fix a couple of bugs it found. Also restructures the pom.xmls to put the modules in the top level so we can order them to have the test plugins build after them. Change-Id: I2f0e4ebd252791fb8844cdf0f635d574946207aa
2017-10-05 02:47:32 +02:00
<module>releng/org.eclipse.cdt.native-feature</module>
<module>releng/org.eclipse.cdt</module>
Bug 558827: Add and/or fix branding on all features Change-Id: I6d8b1ae2416ed673d18e7e15500dcc7c8a87786d
2020-01-06 19:54:46 +01:00
<module>releng/org.eclipse.cdt.platform.branding</module>
Add UI tests plugin for CMake. Fix a couple of bugs it found. Also restructures the pom.xmls to put the modules in the top level so we can order them to have the test plugins build after them. Change-Id: I2f0e4ebd252791fb8844cdf0f635d574946207aa
2017-10-05 02:47:32 +02:00
<module>releng/org.eclipse.cdt.platform-feature</module>
<module>releng/org.eclipse.cdt-feature</module>
<module>releng/org.eclipse.cdt.sdk</module>
<module>releng/org.eclipse.cdt.sdk-feature</module>
<module>releng/org.eclipse.cdt.repo</module>
<module>build/org.eclipse.cdt.managedbuilder.core.tests</module>
<module>build/org.eclipse.cdt.managedbuilder.ui.tests</module>
<module>build/org.eclipse.cdt.make.core.tests</module>
<module>build/org.eclipse.cdt.make.ui.tests</module>
<module>build/org.eclipse.cdt.autotools.tests</module>
<module>build/org.eclipse.cdt.autotools.ui.tests</module>
Enable Meson UI tests Change-Id: I5f0a554c92e1568dd2cda69c198640c2a99769ec
2018-03-29 17:08:33 +02:00
<module>build/org.eclipse.cdt.meson.ui.tests</module>
Add UI tests plugin for CMake. Fix a couple of bugs it found. Also restructures the pom.xmls to put the modules in the top level so we can order them to have the test plugins build after them. Change-Id: I2f0e4ebd252791fb8844cdf0f635d574946207aa
2017-10-05 02:47:32 +02:00
<module>codan/org.eclipse.cdt.codan.core.tests</module>
<module>codan/org.eclipse.cdt.codan.checkers.ui.tests</module>
<module>core/org.eclipse.cdt.core.tests</module>
<module>core/org.eclipse.cdt.ui.tests</module>
<module>dsf-gdb/org.eclipse.cdt.dsf.gdb.tests</module>
<module>dsf-gdb/org.eclipse.cdt.tests.dsf.gdb</module>
<module>dsf-gdb/org.eclipse.cdt.dsf.gdb.multicorevisualizer.ui.tests</module>
Bug 538282: Add GDB Hardware Debugging launch test Change-Id: I308a6a8d128704f83a5fc220c7c168f56e4fc040 Signed-off-by: John Dallaway <john@dallaway.org.uk>
2018-08-26 19:06:35 +02:00
<module>jtag/org.eclipse.cdt.debug.gdbjtag.core.tests</module>
Bug 562164 - Add JUnit tests for IMemoryExporter/ IMemoryImporter Add tests for PlainTextImport/PlainTextExport Add tests for RAWBinaryImport/RAWBinaryExport Add tests for SRecordImport/SRecordExport Change-Id: I4e489498dd6fb451621785743284a31a2f57516f Signed-off-by: Alexander Fedorov <alexander.fedorov@arsysop.ru>
2020-05-03 17:59:22 +02:00
<module>memory/org.eclipse.cdt.debug.core.memory.tests</module>
Add UI tests plugin for CMake. Fix a couple of bugs it found. Also restructures the pom.xmls to put the modules in the top level so we can order them to have the test plugins build after them. Change-Id: I2f0e4ebd252791fb8844cdf0f635d574946207aa
2017-10-05 02:47:32 +02:00
<module>testsrunner/org.eclipse.cdt.testsrunner.tests</module>
<module>releng/org.eclipse.cdt.testing</module>
<module>releng/org.eclipse.cdt.testing-feature</module>
<module>releng/org.eclipse.cdt.testing.repo</module>
<!-- TODO: Investigate/Fix hanging before re-enable re-enabling
<module>debug/org.eclipse.cdt.debug.application.tests</module>
-->
Remove non-functioning Qt plug-ins Fixes #123
2022-10-28 22:51:05 +02:00
Mavenizing CDT releng. Also removed unsupported cdt.core fragments from the platform feature.
2011-06-28 11:21:58 +02:00
</modules>
Fix up signing for master builds. Change-Id: I9c8998be1e6e2db86fa3aae6665f95f6e28888e3 Reviewed-on: https://git.eclipse.org/r/25974 Tested-by: Hudson CI Reviewed-by: Doug Schaefer <dschaefer@qnx.com>
2014-05-05 16:22:34 +02:00
<pluginRepositories>
<pluginRepository>
<id>cbi</id>
Upgrade to Tycho 0.22 Change-Id: I4d4a1f43a27ca286dc04312badc96c9dd775e8af Signed-off-by: Marc-Andre Laperle <marc-andre.laperle@ericsson.com> Reviewed-on: https://git.eclipse.org/r/36953
2014-11-24 20:25:31 +01:00
<url>https://repo.eclipse.org/content/repositories/cbi-releases/</url>
</pluginRepository>
Fix up signing for master builds. Change-Id: I9c8998be1e6e2db86fa3aae6665f95f6e28888e3 Reviewed-on: https://git.eclipse.org/r/25974 Tested-by: Hudson CI Reviewed-by: Doug Schaefer <dschaefer@qnx.com>
2014-05-05 16:22:34 +02:00
</pluginRepositories>
Bug 412057 - UI tests don't run on Mac Cocoa using Tycho build Signed-off-by: Marc-Andre Laperle <marc-andre.laperle@ericsson.com>
2013-07-02 20:30:50 +02:00
<profiles>
Bug 537924: Unable to build javadoc maven target Turns off doclint for Java 1.8 and greater because the javadocs are incomplete and won't build otherwise. Some files also had encoding issues with some characters which caused the javadoc build to fail, these characters have been replaced. Change-Id: I04690644bec6d7c3219cb0438cb3db6593fefd3a Signed-off-by: Hansruedi Patzen <hansruedi.patzen@hsr.ch>
2018-08-13 15:20:06 +02:00
<!-- Turn off doclint because javadocs are incomplete -->
<profile>
<id>disable-java8-doclint</id>
<activation>
<jdk>[1.8,)</jdk>
</activation>
<properties>
<doclint>none</doclint>
</properties>
</profile>
Bug 548526: Enable individual mvn projects to be built Although a little profile "magic" is needed, by adding -DuseSimrelRepo to the command line to enable and disable the correct profiles individual mvn projects can be built against the simrelRepo. This enables, for example, the ability to build the standalone debugger against the simrel repo without having to change how normal builds are done by using: mvn verify -DuseSimrelRepo -f debug/org.eclipse.cdt.debug.application.product A simrel p2 site can also be provided with -Dsimrel-site=<url> Change-Id: I45a636c3c1042bc2fbb6eea5129c6553027e92df
2019-07-16 21:11:49 +02:00
<!--
Individual p2 repos can be turned on and off to allow building CDT, or parts of CDT against
different target platforms easily.
For example, you can:
- test CDT against a pre-built CDT by using the cdtRepo profile.
- build the standalone rcp debugger against the latest simrel
mvn verify -DuseSimrelRepo -f debug/org.eclipse.cdt.debug.application.product
-->
Bug 440153 - Optionally provide an existing CDT repository when doing a maven build Change-Id: Idc3d48bea5625ec84df43ffe50c6940fb4281831 Reviewed-on: https://git.eclipse.org/r/30285 Tested-by: Hudson CI Reviewed-by: Marc-Andre Laperle <marc-andre.laperle@ericsson.com> Reviewed-by: Doug Schaefer <dschaefer@qnx.com> Reviewed-by: Marc Khouzam <marc.khouzam@ericsson.com> Tested-by: Marc Khouzam <marc.khouzam@ericsson.com>
2014-07-22 20:55:22 +02:00
<profile>
<id>cdtRepo</id>
<repositories>
<repository>
<id>cdt.repo</id>
<url>${cdt-site}</url>
<layout>p2</layout>
</repository>
</repositories>
</profile>
Bug 548526: Enable individual mvn projects to be built Although a little profile "magic" is needed, by adding -DuseSimrelRepo to the command line to enable and disable the correct profiles individual mvn projects can be built against the simrelRepo. This enables, for example, the ability to build the standalone debugger against the simrel repo without having to change how normal builds are done by using: mvn verify -DuseSimrelRepo -f debug/org.eclipse.cdt.debug.application.product A simrel p2 site can also be provided with -Dsimrel-site=<url> Change-Id: I45a636c3c1042bc2fbb6eea5129c6553027e92df
2019-07-16 21:11:49 +02:00
<!-- See comment above cdtRepo profile -->
<profile>
<id>simrelRepo</id>
<activation>
<property>
<name>useSimrelRepo</name>
</property>
</activation>
<repositories>
<repository>
<id>simrel.repo</id>
<url>${simrel-site}</url>
<layout>p2</layout>
</repository>
</repositories>
</profile>
<!-- See comment above cdtRepo profile -->
<profile>
<id>defaultCdtTarget</id>
<activation>
<property>
<name>!useSimrelRepo</name>
</property>
</activation>
<build>
<plugins>
<plugin>
<groupId>org.eclipse.tycho</groupId>
<artifactId>target-platform-configuration</artifactId>
<version>${tycho-version}</version>
<configuration>
<target>
Clean up Maven build (#662) * remove invalid tycho resolver config (not valid since many versions) * fix PMD plugin configuration (config attribute was renamed in 3.18) * remove duplicate versions already managed in pluginManagement section * fix indentation * move all not yet configured versions into pluginManagement of the parent module to avoid further duplication * consume the target platform as file, not as maven artifact (this simplifies building a single module A LOT) * remove invalid tycho-source-plugin configuration * disable tycho consumer POM generation (not needed here, and avoids a warning in each module) * remove prerequisites. that's for maven plugins only, and this POM already contains the better suited similar maven enforcer rule * enforce UTF-8 for javadoc generation (the build fails on Windows otherwise, trying to read some Japanese? characters with the Windows default encoding)
2023-12-28 20:35:58 +01:00
<file>${maven.multiModuleProjectDirectory}/releng/org.eclipse.cdt.target/cdt.target</file>
Bug 548526: Enable individual mvn projects to be built Although a little profile "magic" is needed, by adding -DuseSimrelRepo to the command line to enable and disable the correct profiles individual mvn projects can be built against the simrelRepo. This enables, for example, the ability to build the standalone debugger against the simrel repo without having to change how normal builds are done by using: mvn verify -DuseSimrelRepo -f debug/org.eclipse.cdt.debug.application.product A simrel p2 site can also be provided with -Dsimrel-site=<url> Change-Id: I45a636c3c1042bc2fbb6eea5129c6553027e92df
2019-07-16 21:11:49 +02:00
</target>
</configuration>
</plugin>
</plugins>
</build>
</profile>
Bug 412057 - UI tests don't run on Mac Cocoa using Tycho build Signed-off-by: Marc-Andre Laperle <marc-andre.laperle@ericsson.com>
2013-07-02 20:30:50 +02:00
<profile>
<id>macosx</id>
<activation>
<os>
<family>mac</family>
</os>
</activation>
<properties>
Extract test VM args to common property base.test.vmargs This makes it easier to change arguments for all tests. As a side-effect, all tests now enable assertion (-ea) and have the same max heap size, etc. Change-Id: I0965d40ba3283efe7eacdf927f6c302ee0ab30f0 Signed-off-by: Marc-Andre Laperle <marc-andre.laperle@ericsson.com>
2015-02-05 04:31:08 +01:00
<base.ui.test.vmargs>${base.test.vmargs} -XstartOnFirstThread</base.ui.test.vmargs>
Bug 412057 - UI tests don't run on Mac Cocoa using Tycho build Signed-off-by: Marc-Andre Laperle <marc-andre.laperle@ericsson.com>
2013-07-02 20:30:50 +02:00
</properties>
</profile>
<profile>
<id>other-os</id>
<activation>
<os>
<family>!mac</family>
</os>
</activation>
<properties>
Extract test VM args to common property base.test.vmargs This makes it easier to change arguments for all tests. As a side-effect, all tests now enable assertion (-ea) and have the same max heap size, etc. Change-Id: I0965d40ba3283efe7eacdf927f6c302ee0ab30f0 Signed-off-by: Marc-Andre Laperle <marc-andre.laperle@ericsson.com>
2015-02-05 04:31:08 +01:00
<base.ui.test.vmargs>${base.test.vmargs}</base.ui.test.vmargs>
Bug 412057 - UI tests don't run on Mac Cocoa using Tycho build Signed-off-by: Marc-Andre Laperle <marc-andre.laperle@ericsson.com>
2013-07-02 20:30:50 +02:00
</properties>
</profile>
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 22:22:23 +01:00
<!-- Automatic profile for features that shouldn't generate sources -->
<profile>
<id>feature-no-source</id>
<activation>
<file>
<exists>feature-no-source.properties</exists>
</file>
</activation>
<build>
<plugins>
<plugin>
[releng] Fix up usages of tycho-source-plugin Migrate usage of deprecated tycho-source-feature-plugin plugin to the tycho-source-plugin:feature-source goal. Eliminate duplicate invokations of the tycho-source-plugin:plugin-source goal.
2022-10-16 17:51:52 +02:00
<groupId>org.eclipse.tycho</groupId>
<artifactId>tycho-source-plugin</artifactId>
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 22:22:23 +01:00
<executions>
<execution>
[releng] Fix up usages of tycho-source-plugin Migrate usage of deprecated tycho-source-feature-plugin plugin to the tycho-source-plugin:feature-source goal. Eliminate duplicate invokations of the tycho-source-plugin:plugin-source goal.
2022-10-16 17:51:52 +02:00
<id>attach-feature-source</id>
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 22:22:23 +01:00
<phase>none</phase>
</execution>
</executions>
</plugin>
</plugins>
</build>
</profile>
<!-- Automatic profile to define the settings for UI test plugins -->
<profile>
<id>ui-test-plugin</id>
<activation>
<file>
<exists>ui-test-plugin.properties</exists>
</file>
</activation>
<build>
<plugins>
<plugin>
<groupId>org.eclipse.tycho</groupId>
<artifactId>tycho-surefire-plugin</artifactId>
<configuration>
<useUIHarness>true</useUIHarness>
<useUIThread>true</useUIThread>
<argLine>${tycho.testArgLine} ${base.ui.test.vmargs}</argLine>
Move the disable intro ini out of root of repo The root files in GitHub are a bit more prominent, so keep that area clean and move this special ini to a subdir. Change-Id: I12d95727e9dad29ebe4f50d47faa9e98753a52bc
2022-06-26 18:22:45 +02:00
<appArgLine>-pluginCustomization ${basedir}/../../releng/disable_intro_in_tests.ini</appArgLine>
Bug 499777: Don't fail build if no tests are found using tags can cause all tests to be excluded, which is ok and should not fail the build Change-Id: Ia7f5e06c6bfb76df0cd3ac7b5ffe13e555489fad
2021-04-06 23:01:55 +02:00
<!-- using tags can cause all tests to be excluded, which is ok and should not fail the build -->
<failIfNoTests>false</failIfNoTests>
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 22:22:23 +01:00
</configuration>
</plugin>
</plugins>
</build>
</profile>
<!-- Automatic profile to define the settings for SWTBot test plugins -->
<profile>
<id>swtbot-test-plugin</id>
<activation>
<file>
<exists>swtbot-test-plugin.properties</exists>
</file>
</activation>
<build>
<plugins>
<plugin>
<groupId>org.eclipse.tycho</groupId>
<artifactId>tycho-surefire-plugin</artifactId>
<configuration>
<useUIHarness>true</useUIHarness>
<useUIThread>false</useUIThread>
<argLine>${tycho.testArgLine} ${base.ui.test.vmargs}</argLine>
Move the disable intro ini out of root of repo The root files in GitHub are a bit more prominent, so keep that area clean and move this special ini to a subdir. Change-Id: I12d95727e9dad29ebe4f50d47faa9e98753a52bc
2022-06-26 18:22:45 +02:00
<appArgLine>-pluginCustomization ${basedir}/../../releng/disable_intro_in_tests.ini</appArgLine>
Bug 499777: Don't fail build if no tests are found using tags can cause all tests to be excluded, which is ok and should not fail the build Change-Id: Ia7f5e06c6bfb76df0cd3ac7b5ffe13e555489fad
2021-04-06 23:01:55 +02:00
<!-- using tags can cause all tests to be excluded, which is ok and should not fail the build -->
<failIfNoTests>false</failIfNoTests>
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 22:22:23 +01:00
</configuration>
</plugin>
</plugins>
</build>
</profile>
Bug 558827: Add build id timestamp to features properly This was lost when the build system was moved to Maven/Tycho for CDT 8 and restores the information. Note that with the p2 baseline compare and replace this will show the build id of when the branding plugin (the one with the about.mappings) was built, which compared to the feature version may be older. The about.mappings, as it is generated on each build, is ignored from p2 compare and replace. Change-Id: I38d1fcc5f618d4037baa2c8b908952421c712fc6
2020-01-06 18:03:23 +01:00
<profile>
<id>about-mappings</id>
<activation>
<file>
<exists>about.mappings</exists>
</file>
</activation>
<build>
<resources>
<resource>
<directory>.</directory>
<filtering>true</filtering>
<includes>
<include>about.mappings</include>
</includes>
</resource>
</resources>
</build>
</profile>
Bug 515304: profiles to parallelize testsuite Change-Id: I02095334c2176bfb9a2968d91b6175af37123f5b Signed-off-by: Jonah Graham <jonah@kichwacoders.com>
2017-04-15 01:14:38 +02:00
<profile>
<id>skip-all-tests</id>
<properties>
<cdt-ui.skip.tests>true</cdt-ui.skip.tests>
<dsf-gdb.skip.tests>true</dsf-gdb.skip.tests>
<cdt-other.skip.tests>true</cdt-other.skip.tests>
</properties>
</profile>
<profile>
<id>skip-tests-except-cdt-ui</id>
<properties>
<dsf-gdb.skip.tests>true</dsf-gdb.skip.tests>
<cdt-other.skip.tests>true</cdt-other.skip.tests>
</properties>
</profile>
<profile>
<id>skip-tests-except-dsf-gdb</id>
<properties>
<cdt-ui.skip.tests>true</cdt-ui.skip.tests>
<cdt-other.skip.tests>true</cdt-other.skip.tests>
</properties>
</profile>
<profile>
<id>skip-tests-except-cdt-other</id>
<properties>
<cdt-ui.skip.tests>true</cdt-ui.skip.tests>
<dsf-gdb.skip.tests>true</dsf-gdb.skip.tests>
</properties>
</profile>
Bug 547894: Provide a way to skip baseline replace and compare Change-Id: If8080db7374eabb7a640deba0fab1e26a785ac5c
2019-06-26 15:56:49 +02:00
<profile>
[releng] Change default to be baseline compare and replace is not run Use baseline-compare-and-replace profile to run it. Change-Id: Iaacfad8f920f28cf773763e804be90ba8c5f30cf
2019-07-03 19:56:07 +02:00
<id>baseline-compare-and-replace</id>
Bug 547894: Provide a way to skip baseline replace and compare Change-Id: If8080db7374eabb7a640deba0fab1e26a785ac5c
2019-06-26 15:56:49 +02:00
<properties>
[releng] Change default to be baseline compare and replace is not run Use baseline-compare-and-replace profile to run it. Change-Id: Iaacfad8f920f28cf773763e804be90ba8c5f30cf
2019-07-03 19:56:07 +02:00
<compare-version-with-baselines.skip>false</compare-version-with-baselines.skip>
<replace-version-with-baselines.mode>fail</replace-version-with-baselines.mode>
<replace-version-with-baselines.replace>all</replace-version-with-baselines.replace>
Bug 547894: Provide a way to skip baseline replace and compare Change-Id: If8080db7374eabb7a640deba0fab1e26a785ac5c
2019-06-26 15:56:49 +02:00
</properties>
</profile>
Add API Baseline checking to the build
2023-08-16 21:22:28 +02:00
<profile>
<id>api-baseline-check</id>
<build>
<plugins>
<plugin>
<groupId>org.eclipse.tycho</groupId>
<artifactId>tycho-apitools-plugin</artifactId>
<version>${tycho-version}</version>
<configuration>
<skipIfReplaced>false</skipIfReplaced>
<baselines>
<repository>
<url>${api-baseline.repo}</url>
Fix multiple repositories in API baseline This happened to work before because the contents of api-baseline.repo was in api-baseline.repo.simrel so the error in the pom.xml went undetected until #551 issue meant api-baseline.repo wasn't in api-baseline.repo.simrel
2023-09-15 15:11:14 +02:00
</repository>
<repository>
Add API Baseline checking to the build
2023-08-16 21:22:28 +02:00
<url>${api-baseline.repo.simrel}</url>
</repository>
</baselines>
</configuration>
<executions>
<execution>
<id>generate</id>
<goals>
<goal>generate</goal>
</goals>
</execution>
<execution>
<id>verify</id>
<goals>
<goal>verify</goal>
</goals>
</execution>
</executions>
</plugin>
</plugins>
</build>
</profile>
Fix up signing for master builds. Change-Id: I9c8998be1e6e2db86fa3aae6665f95f6e28888e3 Reviewed-on: https://git.eclipse.org/r/25974 Tested-by: Hudson CI Reviewed-by: Doug Schaefer <dschaefer@qnx.com>
2014-05-05 16:22:34 +02:00
<profile>
<id>production</id>
<build>
<plugins>
<plugin>
<groupId>org.eclipse.tycho</groupId>
<artifactId>target-platform-configuration</artifactId>
<version>${tycho-version}</version>
<configuration>
Bug 457495 - Include packed jars for CDT builds With this change the build will now contain the packed jars for each plugin. They can be seen under releng/org.eclipse.cdt.repo/target/repository/plugins/*pack.gz. Those packed jars are removed from the zip file as they just duplicate the existing jars. Change-Id: Ida5804e6939f1dd99a5cc169518738bb394198a6 Signed-off-by: Marc Khouzam <marc.khouzam@ericsson.com>
2015-01-14 21:15:35 +01:00
<includePackedArtifacts>true</includePackedArtifacts>
Fix up signing for master builds. Change-Id: I9c8998be1e6e2db86fa3aae6665f95f6e28888e3 Reviewed-on: https://git.eclipse.org/r/25974 Tested-by: Hudson CI Reviewed-by: Doug Schaefer <dschaefer@qnx.com>
2014-05-05 16:22:34 +02:00
</configuration>
</plugin>
<plugin>
<groupId>org.eclipse.cbi.maven.plugins</groupId>
<artifactId>eclipse-jarsigner-plugin</artifactId>
Sign the stand-alone debugger on Mac The mac signing has to happen between materialize-products and archive-products goals. Because we only want to do it when the production profile is enabled (eclipse.org server), we have to duplicate some xml to fit the macsigner between the two. I did extract some variables in order to make the duplication less error prone. Change-Id: I523c287c0e1dff15026e1007fa2831af6d14003a Signed-off-by: Marc-Andre Laperle <marc-andre.laperle@ericsson.com>
2016-05-27 07:24:29 +02:00
<version>${cbi-plugins.version}</version>
Fix up signing for master builds. Change-Id: I9c8998be1e6e2db86fa3aae6665f95f6e28888e3 Reviewed-on: https://git.eclipse.org/r/25974 Tested-by: Hudson CI Reviewed-by: Doug Schaefer <dschaefer@qnx.com>
2014-05-05 16:22:34 +02:00
<executions>
<execution>
<id>sign</id>
<phase>verify</phase>
<goals>
<goal>sign</goal>
</goals>
</execution>
</executions>
</plugin>
<plugin>
<groupId>org.eclipse.tycho</groupId>
<artifactId>tycho-p2-plugin</artifactId>
<version>${tycho-version}</version>
<executions>
<execution>
<id>p2-metadata</id>
<goals>
<goal>p2-metadata</goal>
</goals>
<phase>verify</phase>
</execution>
</executions>
<configuration>
<defaultP2Metadata>false</defaultP2Metadata>
</configuration>
</plugin>
</plugins>
</build>
</profile>
Bug 412057 - UI tests don't run on Mac Cocoa using Tycho build Signed-off-by: Marc-Andre Laperle <marc-andre.laperle@ericsson.com>
2013-07-02 20:30:50 +02:00
</profiles>
Mavenizing CDT releng. Also removed unsupported cdt.core fragments from the platform feature.
2011-06-28 11:21:58 +02:00
<build>
<plugins>
[releng] Enforce Maven version to 3.6.0 See Bug 551674. This commit also moves the enforcer plug-in into the correct place to be activated The enforcer plug-in needs to be done to allow the check maven versions to not report erroneous/extra information too (see next commit) Change-Id: I2da89b0a9ec0fc3dc27f0812fef53104dcaa7fd6
2019-11-07 23:24:53 +01:00
<plugin>
<inherited>true</inherited>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-enforcer-plugin</artifactId>
Update maven plugins maven-enforcer-plugin 3.2.1 -> 3.4.1 maven-pmd-plugin 3.20.0 -> 3.21.2 maven-resources-plugin 3.3.0 -> 3.3.1 org.codehaus.mojo:build-helper-maven-plugin 3.4.0 -> 3.5.0 org.codehaus.mojo:sonar-maven-plugin 2.4 -> 3.10.0.2594 org.jacoco:jacoco-maven-plugin 0.8.8 -> 0.8.11
2024-02-21 16:09:40 +01:00
<version>3.4.1</version>
[releng] Enforce Maven version to 3.6.0 See Bug 551674. This commit also moves the enforcer plug-in into the correct place to be activated The enforcer plug-in needs to be done to allow the check maven versions to not report erroneous/extra information too (see next commit) Change-Id: I2da89b0a9ec0fc3dc27f0812fef53104dcaa7fd6
2019-11-07 23:24:53 +01:00
<executions>
<execution>
<id>enforce-maven-version</id>
<goals>
<goal>enforce</goal>
</goals>
<configuration>
<rules>
<requireMavenVersion>
<version>${required-maven-version}</version>
</requireMavenVersion>
<requireJavaVersion>
[#657] CDT cannot be built on Java 21 due to security manager changes * Switch CI to Java 21 * Remove config generation for debug application * Remove `org.eclipse.osgi.services` from `proxy.server` product * Remove `org.eclipse.osgi.services` from `org.eclipse.cdt.debug.application.product` product * Move `org.eclipse.cdt.debug.application.product` from profile to general part Signed-off-by: Alexander Fedorov <alexander.fedorov@arsysop.ru>
2024-04-19 17:21:37 +02:00
<version>21</version>
[releng] Enforce Maven version to 3.6.0 See Bug 551674. This commit also moves the enforcer plug-in into the correct place to be activated The enforcer plug-in needs to be done to allow the check maven versions to not report erroneous/extra information too (see next commit) Change-Id: I2da89b0a9ec0fc3dc27f0812fef53104dcaa7fd6
2019-11-07 23:24:53 +01:00
</requireJavaVersion>
</rules>
<fail>true</fail>
<failFast>true</failFast>
</configuration>
</execution>
</executions>
</plugin>
Fix sonar plug-in version due to problem with most recent version. Change-Id: Id4d6c41019adc633aeef668c89af9f9c1995e832
2017-05-08 22:58:56 +02:00
<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>sonar-maven-plugin</artifactId>
Update maven plugins maven-enforcer-plugin 3.2.1 -> 3.4.1 maven-pmd-plugin 3.20.0 -> 3.21.2 maven-resources-plugin 3.3.0 -> 3.3.1 org.codehaus.mojo:build-helper-maven-plugin 3.4.0 -> 3.5.0 org.codehaus.mojo:sonar-maven-plugin 2.4 -> 3.10.0.2594 org.jacoco:jacoco-maven-plugin 0.8.8 -> 0.8.11
2024-02-21 16:09:40 +01:00
<version>3.10.0.2594</version>
Fix sonar plug-in version due to problem with most recent version. Change-Id: Id4d6c41019adc633aeef668c89af9f9c1995e832
2017-05-08 22:58:56 +02:00
</plugin>
Mavenizing CDT releng. Also removed unsupported cdt.core fragments from the platform feature.
2011-06-28 11:21:58 +02:00
<plugin>
<groupId>org.eclipse.tycho</groupId>
<artifactId>tycho-maven-plugin</artifactId>
<version>${tycho-version}</version>
<extensions>true</extensions>
</plugin>
<plugin>
<groupId>org.eclipse.tycho</groupId>
<artifactId>target-platform-configuration</artifactId>
<version>${tycho-version}</version>
<configuration>
<pomDependencies>consider</pomDependencies>
<environments>
<environment>
<os>linux</os>
<ws>gtk</ws>
<arch>x86_64</arch>
</environment>
Bug 565836: Add linux aarch64 for natives Note: the Windows dll is not actually modified, apart from the embedded date stamp to match the date of the jni/ modification Also-by: Liviu Ionescu <ilg@livius.net> Change-Id: Ice3d5e7ae5999a0e4d1866e76e515a91e30e9f11
2020-08-07 02:59:35 +02:00
<environment>
<os>linux</os>
<ws>gtk</ws>
<arch>aarch64</arch>
</environment>
Remove profiles that helped skip ppc64le Those profiles were useful when keeping compatibility with Eclipse 4.5 but this is not required anymore. Change-Id: Ic9ef7beecee1b5bd072ec192048ab409b19844c9 Signed-off-by: Marc-Andre Laperle <marc-andre.laperle@ericsson.com>
2017-02-05 06:40:01 +01:00
<environment>
<os>linux</os>
<ws>gtk</ws>
<arch>ppc64le</arch>
</environment>
Mavenizing CDT releng. Also removed unsupported cdt.core fragments from the platform feature.
2011-06-28 11:21:58 +02:00
<environment>
<os>win32</os>
<ws>win32</ws>
<arch>x86_64</arch>
</environment>
<environment>
<os>macosx</os>
<ws>cocoa</ws>
<arch>x86_64</arch>
</environment>
Bug 576533: Add support for Mac M1 -framework JavaVM is no longer needed for a while and in latest Xcode is removed as an option x86 on macOS is no longer supported by recent Xcode, so drop it from CDT. x86 hasn't been supported in Platform for a while, so it wasn't actually usable. Change-Id: I149722b168fe9819ee334d4afd25ae624b1664c5
2021-11-15 21:14:27 +01:00
<environment>
<os>macosx</os>
<ws>cocoa</ws>
<arch>aarch64</arch>
</environment>
Mavenizing CDT releng. Also removed unsupported cdt.core fragments from the platform feature.
2011-06-28 11:21:58 +02:00
</environments>
Bug 577097: Integrate o.e.remote releng into CDT Change-Id: I55fbfcfae1c414ae21807473f4ab290db40b5238
2021-12-14 20:33:36 +01:00
<dependency-resolution>
<extraRequirements>
<requirement>
<type>eclipse-plugin</type>
<id>org.eclipse.ui.ide</id>
<versionRange>0.0.0</versionRange>
</requirement>
</extraRequirements>
</dependency-resolution>
Mavenizing CDT releng. Also removed unsupported cdt.core fragments from the platform feature.
2011-06-28 11:21:58 +02:00
</configuration>
</plugin>
<plugin>
<groupId>org.eclipse.tycho</groupId>
<artifactId>tycho-source-plugin</artifactId>
<executions>
<execution>
<id>attach-source</id>
<goals>
<goal>plugin-source</goal>
</goals>
</execution>
Auto-generate source features using tycho. This commit removes explicit source features and has tycho create them automatically, along with all other source features that were not previously defined. The logic to auto-generate is in the root pom.xml For all pre-existing source feature, the name presented to the user has been changed to use the default name used by Tycho, which is "Developer Resources". This will provide a more standard user-experience with respect to other source features built by Tycho. Existing SDK features are kept for backwards compatibility. All the names of the auto-generated source features that replace an existing source feature have stayed the same except for the 'testsrunner' feature; for that one name change, a p2.inf file is added to allow upgrading from the old named feature to the new named feature. Change-Id: Ie632e798c93898fd828f88df4983fc43e2749d22
2016-12-05 18:55:10 +01:00
<execution>
[releng] Fix up usages of tycho-source-plugin Migrate usage of deprecated tycho-source-feature-plugin plugin to the tycho-source-plugin:feature-source goal. Eliminate duplicate invokations of the tycho-source-plugin:plugin-source goal.
2022-10-16 17:51:52 +02:00
<id>attach-feature-source</id>
Auto-generate source features using tycho. This commit removes explicit source features and has tycho create them automatically, along with all other source features that were not previously defined. The logic to auto-generate is in the root pom.xml For all pre-existing source feature, the name presented to the user has been changed to use the default name used by Tycho, which is "Developer Resources". This will provide a more standard user-experience with respect to other source features built by Tycho. Existing SDK features are kept for backwards compatibility. All the names of the auto-generated source features that replace an existing source feature have stayed the same except for the 'testsrunner' feature; for that one name change, a p2.inf file is added to allow upgrading from the old named feature to the new named feature. Change-Id: Ie632e798c93898fd828f88df4983fc43e2749d22
2016-12-05 18:55:10 +01:00
<phase>package</phase>
<goals>
[releng] Fix up usages of tycho-source-plugin Migrate usage of deprecated tycho-source-feature-plugin plugin to the tycho-source-plugin:feature-source goal. Eliminate duplicate invokations of the tycho-source-plugin:plugin-source goal.
2022-10-16 17:51:52 +02:00
<goal>feature-source</goal>
Auto-generate source features using tycho. This commit removes explicit source features and has tycho create them automatically, along with all other source features that were not previously defined. The logic to auto-generate is in the root pom.xml For all pre-existing source feature, the name presented to the user has been changed to use the default name used by Tycho, which is "Developer Resources". This will provide a more standard user-experience with respect to other source features built by Tycho. Existing SDK features are kept for backwards compatibility. All the names of the auto-generated source features that replace an existing source feature have stayed the same except for the 'testsrunner' feature; for that one name change, a p2.inf file is added to allow upgrading from the old named feature to the new named feature. Change-Id: Ie632e798c93898fd828f88df4983fc43e2749d22
2016-12-05 18:55:10 +01:00
</goals>
<configuration>
[releng] Fix up usages of tycho-source-plugin Migrate usage of deprecated tycho-source-feature-plugin plugin to the tycho-source-plugin:feature-source goal. Eliminate duplicate invokations of the tycho-source-plugin:plugin-source goal.
2022-10-16 17:51:52 +02:00
<includeBinaryFeature>false</includeBinaryFeature>
Auto-generate source features using tycho. This commit removes explicit source features and has tycho create them automatically, along with all other source features that were not previously defined. The logic to auto-generate is in the root pom.xml For all pre-existing source feature, the name presented to the user has been changed to use the default name used by Tycho, which is "Developer Resources". This will provide a more standard user-experience with respect to other source features built by Tycho. Existing SDK features are kept for backwards compatibility. All the names of the auto-generated source features that replace an existing source feature have stayed the same except for the 'testsrunner' feature; for that one name change, a p2.inf file is added to allow upgrading from the old named feature to the new named feature. Change-Id: Ie632e798c93898fd828f88df4983fc43e2749d22
2016-12-05 18:55:10 +01:00
<excludes>
<plugin id="org.eclipse.cdt.autotools.docs"/>
Add Meson docs plug-in Change-Id: I9153edd6f2708de475855ca3dbdb6323432e37ac
2018-03-06 23:16:48 +01:00
<plugin id="org.eclipse.cdt.meson.docs"/>
Auto-generate source features using tycho. This commit removes explicit source features and has tycho create them automatically, along with all other source features that were not previously defined. The logic to auto-generate is in the root pom.xml For all pre-existing source feature, the name presented to the user has been changed to use the default name used by Tycho, which is "Developer Resources". This will provide a more standard user-experience with respect to other source features built by Tycho. Existing SDK features are kept for backwards compatibility. All the names of the auto-generated source features that replace an existing source feature have stayed the same except for the 'testsrunner' feature; for that one name change, a p2.inf file is added to allow upgrading from the old named feature to the new named feature. Change-Id: Ie632e798c93898fd828f88df4983fc43e2749d22
2016-12-05 18:55:10 +01:00
<plugin id="org.eclipse.cdt.core.linux.ppc64le"/>
<plugin id="org.eclipse.cdt.core.linux.x86_64"/>
Bug 565836: Add linux aarch64 for natives Note: the Windows dll is not actually modified, apart from the embedded date stamp to match the date of the jni/ modification Also-by: Liviu Ionescu <ilg@livius.net> Change-Id: Ice3d5e7ae5999a0e4d1866e76e515a91e30e9f11
2020-08-07 02:59:35 +02:00
<plugin id="org.eclipse.cdt.core.linux.aarch64"/>
Auto-generate source features using tycho. This commit removes explicit source features and has tycho create them automatically, along with all other source features that were not previously defined. The logic to auto-generate is in the root pom.xml For all pre-existing source feature, the name presented to the user has been changed to use the default name used by Tycho, which is "Developer Resources". This will provide a more standard user-experience with respect to other source features built by Tycho. Existing SDK features are kept for backwards compatibility. All the names of the auto-generated source features that replace an existing source feature have stayed the same except for the 'testsrunner' feature; for that one name change, a p2.inf file is added to allow upgrading from the old named feature to the new named feature. Change-Id: Ie632e798c93898fd828f88df4983fc43e2749d22
2016-12-05 18:55:10 +01:00
<plugin id="org.eclipse.cdt.core.win32.x86_64"/>
<plugin id="org.eclipse.cdt.doc.user"/>
<plugin id="org.eclipse.cdt.debug.gdbjtag"/>
<plugin id="org.eclipse.cdt"/>
<plugin id="net.sourceforge.lpg.lpgjavaruntime"/>
<plugin id="org.eclipse.ant.optional.junit"/>
<plugin id="org.eclipse.cdt.testing"/>
Bug 577097: Integrate o.e.remote releng into CDT Change-Id: I55fbfcfae1c414ae21807473f4ab290db40b5238
2021-12-14 20:33:36 +01:00
<plugin id="org.eclipse.remote.proxy.server.linux.x86_64"/>
<plugin id="org.eclipse.remote.proxy.server.linux.ppc64le"/>
<plugin id="org.eclipse.remote.proxy.server.macosx.x86_64"/>
<plugin id="org.eclipse.remote.doc.isv"/>
Auto-generate source features using tycho. This commit removes explicit source features and has tycho create them automatically, along with all other source features that were not previously defined. The logic to auto-generate is in the root pom.xml For all pre-existing source feature, the name presented to the user has been changed to use the default name used by Tycho, which is "Developer Resources". This will provide a more standard user-experience with respect to other source features built by Tycho. Existing SDK features are kept for backwards compatibility. All the names of the auto-generated source features that replace an existing source feature have stayed the same except for the 'testsrunner' feature; for that one name change, a p2.inf file is added to allow upgrading from the old named feature to the new named feature. Change-Id: Ie632e798c93898fd828f88df4983fc43e2749d22
2016-12-05 18:55:10 +01:00
</excludes>
</configuration>
</execution>
</executions>
</plugin>
<plugin>
<groupId>org.eclipse.tycho</groupId>
<artifactId>tycho-p2-plugin</artifactId>
<executions>
<execution>
<id>attached-p2-metadata</id>
<phase>package</phase>
<goals>
<goal>p2-metadata</goal>
</goals>
</execution>
</executions>
</plugin>
Add support for Sonar reporting. Change-Id: Ibd6bf69cb88ae41f0e768d5ac50656589eb00ec0 Reviewed-on: https://git.eclipse.org/r/14717 Reviewed-by: Jeff Johnston <jjohnstn@redhat.com> IP-Clean: Jeff Johnston <jjohnstn@redhat.com> Tested-by: Jeff Johnston <jjohnstn@redhat.com>
2013-07-20 00:54:21 +02:00
<plugin>
<groupId>org.jacoco</groupId>
<artifactId>jacoco-maven-plugin</artifactId>
Update maven plugins maven-enforcer-plugin 3.2.1 -> 3.4.1 maven-pmd-plugin 3.20.0 -> 3.21.2 maven-resources-plugin 3.3.0 -> 3.3.1 org.codehaus.mojo:build-helper-maven-plugin 3.4.0 -> 3.5.0 org.codehaus.mojo:sonar-maven-plugin 2.4 -> 3.10.0.2594 org.jacoco:jacoco-maven-plugin 0.8.8 -> 0.8.11
2024-02-21 16:09:40 +01:00
<version>0.8.11</version>
Add support for Sonar reporting. Change-Id: Ibd6bf69cb88ae41f0e768d5ac50656589eb00ec0 Reviewed-on: https://git.eclipse.org/r/14717 Reviewed-by: Jeff Johnston <jjohnstn@redhat.com> IP-Clean: Jeff Johnston <jjohnstn@redhat.com> Tested-by: Jeff Johnston <jjohnstn@redhat.com>
2013-07-20 00:54:21 +02:00
<executions>
<execution>
<id>pre-test</id>
<goals>
<goal>prepare-agent</goal>
</goals>
<configuration>
<!-- Where to put jacoco coverage report -->
<destFile>${sonar.jacoco.reportPath}</destFile>
<includes>
<include>org.eclipse.cdt.*</include>
</includes>
<append>true</append>
</configuration>
</execution>
</executions>
</plugin>
Bug 540367 - Enable Reproducible Version Qualifiers Change-Id: I1ccd2330951a83a7632c67a6274b7527cd9f237c
2018-10-22 16:09:31 +02:00
<plugin>
<groupId>org.eclipse.tycho.extras</groupId>
<artifactId>tycho-p2-extras-plugin</artifactId>
<version>${tycho-version}</version>
<executions>
<execution> <!-- Checks versions are properly bumped from one stream to the other -->
<id>compare-attached-artifacts-with-release</id>
<goals>
<goal>compare-version-with-baselines</goal>
</goals>
<configuration>
<skip>${compare-version-with-baselines.skip}</skip>
<baselines>
<baseline>${comparator.repo}</baseline> <!-- Previous release) -->
</baselines>
<comparator>zip</comparator>
</configuration>
</execution>
</executions>
</plugin>
Mavenizing CDT releng. Also removed unsupported cdt.core fragments from the platform feature.
2011-06-28 11:21:58 +02:00
</plugins>
<pluginManagement>
<plugins>
<plugin>
<groupId>org.eclipse.tycho</groupId>
<artifactId>tycho-compiler-plugin</artifactId>
<version>${tycho-version}</version>
<configuration>
<encoding>UTF-8</encoding>
</configuration>
</plugin>
<!-- enable source bundle generation -->
<plugin>
<groupId>org.eclipse.tycho</groupId>
<artifactId>tycho-source-plugin</artifactId>
<version>${tycho-version}</version>
</plugin>
Add SourceReferences to plugins This allows the user to clone and checkout the source code of CDT without knowing where the repository is. See: https://wiki.eclipse.org/PDE/UI/SourceReferences One use case is to right-click on a plug-in under the Plug-in dependencies in Package Explorer view and select Import from Repository. Note that for this EGit needs to be installed. What this patch does is to let Tycho generate the source references in the MANIFEST.MF of the built jars. So to test this patch, one can build the update site locally and inspect the manifests of the (non-source) jars. Change-Id: I807cd7842e3485ae1affcaa03ae08bdbb1677c97 Signed-off-by: Marc-Andre Laperle <marc-andre.laperle@ericsson.com> Reviewed-on: https://git.eclipse.org/r/39549 Tested-by: Hudson CI Reviewed-by: Alvaro Sanchez-Leon <alvsan09@gmail.com> Tested-by: Alvaro Sanchez-Leon <alvsan09@gmail.com>
2015-01-14 05:18:44 +01:00
<plugin>
<groupId>org.eclipse.tycho</groupId>
<artifactId>tycho-packaging-plugin</artifactId>
<version>${tycho-version}</version>
<configuration>
[releng] Update to newer Tycho Newer Tycho has a new feature that adds an extra header (Bundle-License) to every plug-in. This commit includes omitting this new feature rather than bumping every single version of every bundle in CDT. See https://www.eclipse.org/tycho/sitedocs/tycho-packaging-plugin/package-plugin-mojo.html#deriveHeaderFromProject Bundles have version bumps due to newer Tycho including newer JDT compiler which leads to classfile differences. Change-Id: Id536d75a92a30582418324e27d74008869f7dd3a
2021-09-23 20:34:25 +02:00
<deriveHeaderFromProject>false</deriveHeaderFromProject>
Restore BREE headers to all MANIFEST.MF Fixes #551
2023-09-14 22:28:57 +02:00
<deriveHeaderFromSource>false</deriveHeaderFromSource>
Bug 540367 - Enable Reproducible Version Qualifiers Change-Id: I1ccd2330951a83a7632c67a6274b7527cd9f237c
2018-10-22 16:09:31 +02:00
<format>${qualifier.format}</format>
<timestampProvider>jgit</timestampProvider>
<jgit.ignore>
pom.xml
Build with Tycho 2.0.0 Change-Id: I2b47317f35c990f222b43cc14837d0281b8e3bfe Signed-off-by: Alexander Kurtakov <akurtako@redhat.com>
2020-09-29 17:31:07 +02:00
.polyglot.*
Bug 540367 - Enable Reproducible Version Qualifiers Change-Id: I1ccd2330951a83a7632c67a6274b7527cd9f237c
2018-10-22 16:09:31 +02:00
</jgit.ignore>
<jgit.dirtyWorkingTree>${jgit.dirtyWorkingTree-cdtDefault}</jgit.dirtyWorkingTree>
Add SourceReferences to plugins This allows the user to clone and checkout the source code of CDT without knowing where the repository is. See: https://wiki.eclipse.org/PDE/UI/SourceReferences One use case is to right-click on a plug-in under the Plug-in dependencies in Package Explorer view and select Import from Repository. Note that for this EGit needs to be installed. What this patch does is to let Tycho generate the source references in the MANIFEST.MF of the built jars. So to test this patch, one can build the update site locally and inspect the manifests of the (non-source) jars. Change-Id: I807cd7842e3485ae1affcaa03ae08bdbb1677c97 Signed-off-by: Marc-Andre Laperle <marc-andre.laperle@ericsson.com> Reviewed-on: https://git.eclipse.org/r/39549 Tested-by: Hudson CI Reviewed-by: Alvaro Sanchez-Leon <alvsan09@gmail.com> Tested-by: Alvaro Sanchez-Leon <alvsan09@gmail.com>
2015-01-14 05:18:44 +01:00
<sourceReferences>
<generate>true</generate>
</sourceReferences>
Bug 558827: Add build id timestamp to features properly This was lost when the build system was moved to Maven/Tycho for CDT 8 and restores the information. Note that with the p2 baseline compare and replace this will show the build id of when the branding plugin (the one with the about.mappings) was built, which compared to the feature version may be older. The about.mappings, as it is generated on each build, is ignored from p2 compare and replace. Change-Id: I38d1fcc5f618d4037baa2c8b908952421c712fc6
2020-01-06 18:03:23 +01:00
<additionalFileSets>
<fileSet>
<directory>${project.build.outputDirectory}</directory>
<includes>
<include>about.mappings</include>
</includes>
</fileSet>
</additionalFileSets>
Add SourceReferences to plugins This allows the user to clone and checkout the source code of CDT without knowing where the repository is. See: https://wiki.eclipse.org/PDE/UI/SourceReferences One use case is to right-click on a plug-in under the Plug-in dependencies in Package Explorer view and select Import from Repository. Note that for this EGit needs to be installed. What this patch does is to let Tycho generate the source references in the MANIFEST.MF of the built jars. So to test this patch, one can build the update site locally and inspect the manifests of the (non-source) jars. Change-Id: I807cd7842e3485ae1affcaa03ae08bdbb1677c97 Signed-off-by: Marc-Andre Laperle <marc-andre.laperle@ericsson.com> Reviewed-on: https://git.eclipse.org/r/39549 Tested-by: Hudson CI Reviewed-by: Alvaro Sanchez-Leon <alvsan09@gmail.com> Tested-by: Alvaro Sanchez-Leon <alvsan09@gmail.com>
2015-01-14 05:18:44 +01:00
</configuration>
<dependencies>
Bug 540367 - Enable Reproducible Version Qualifiers Change-Id: I1ccd2330951a83a7632c67a6274b7527cd9f237c
2018-10-22 16:09:31 +02:00
<dependency>
Upgrade to Tycho 3.0.3 (latest) Part of #320 See also #308
2023-03-13 19:25:58 +01:00
<groupId>org.eclipse.tycho</groupId>
Bug 540367 - Enable Reproducible Version Qualifiers Change-Id: I1ccd2330951a83a7632c67a6274b7527cd9f237c
2018-10-22 16:09:31 +02:00
<artifactId>tycho-buildtimestamp-jgit</artifactId>
Build with Tycho 1.7.0 Get rid of tycho-extras-version as there is no more tycho-extras. Change-Id: I9d215aad94c4e8320153f06368d6b3ecfa4a3c42 Signed-off-by: Alexander Kurtakov <akurtako@redhat.com>
2020-07-22 08:21:27 +02:00
<version>${tycho-version}</version>
Bug 540367 - Enable Reproducible Version Qualifiers Change-Id: I1ccd2330951a83a7632c67a6274b7527cd9f237c
2018-10-22 16:09:31 +02:00
</dependency>
Add SourceReferences to plugins This allows the user to clone and checkout the source code of CDT without knowing where the repository is. See: https://wiki.eclipse.org/PDE/UI/SourceReferences One use case is to right-click on a plug-in under the Plug-in dependencies in Package Explorer view and select Import from Repository. Note that for this EGit needs to be installed. What this patch does is to let Tycho generate the source references in the MANIFEST.MF of the built jars. So to test this patch, one can build the update site locally and inspect the manifests of the (non-source) jars. Change-Id: I807cd7842e3485ae1affcaa03ae08bdbb1677c97 Signed-off-by: Marc-Andre Laperle <marc-andre.laperle@ericsson.com> Reviewed-on: https://git.eclipse.org/r/39549 Tested-by: Hudson CI Reviewed-by: Alvaro Sanchez-Leon <alvsan09@gmail.com> Tested-by: Alvaro Sanchez-Leon <alvsan09@gmail.com>
2015-01-14 05:18:44 +01:00
<dependency>
<groupId>org.eclipse.tycho.extras</groupId>
<artifactId>tycho-sourceref-jgit</artifactId>
Build with Tycho 1.7.0 Get rid of tycho-extras-version as there is no more tycho-extras. Change-Id: I9d215aad94c4e8320153f06368d6b3ecfa4a3c42 Signed-off-by: Alexander Kurtakov <akurtako@redhat.com>
2020-07-22 08:21:27 +02:00
<version>${tycho-version}</version>
Add SourceReferences to plugins This allows the user to clone and checkout the source code of CDT without knowing where the repository is. See: https://wiki.eclipse.org/PDE/UI/SourceReferences One use case is to right-click on a plug-in under the Plug-in dependencies in Package Explorer view and select Import from Repository. Note that for this EGit needs to be installed. What this patch does is to let Tycho generate the source references in the MANIFEST.MF of the built jars. So to test this patch, one can build the update site locally and inspect the manifests of the (non-source) jars. Change-Id: I807cd7842e3485ae1affcaa03ae08bdbb1677c97 Signed-off-by: Marc-Andre Laperle <marc-andre.laperle@ericsson.com> Reviewed-on: https://git.eclipse.org/r/39549 Tested-by: Hudson CI Reviewed-by: Alvaro Sanchez-Leon <alvsan09@gmail.com> Tested-by: Alvaro Sanchez-Leon <alvsan09@gmail.com>
2015-01-14 05:18:44 +01:00
</dependency>
</dependencies>
Clean up Maven build (#662) * remove invalid tycho resolver config (not valid since many versions) * fix PMD plugin configuration (config attribute was renamed in 3.18) * remove duplicate versions already managed in pluginManagement section * fix indentation * move all not yet configured versions into pluginManagement of the parent module to avoid further duplication * consume the target platform as file, not as maven artifact (this simplifies building a single module A LOT) * remove invalid tycho-source-plugin configuration * disable tycho consumer POM generation (not needed here, and avoids a warning in each module) * remove prerequisites. that's for maven plugins only, and this POM already contains the better suited similar maven enforcer rule * enforce UTF-8 for javadoc generation (the build fails on Windows otherwise, trying to read some Japanese? characters with the Windows default encoding)
2023-12-28 20:35:58 +01:00
<executions>
<execution>
<!-- disable default consumer pom. not needed here, and it shows a warning for each module -->
<id>default-update-consumer-pom</id>
<phase>none</phase>
</execution>
</executions>
Add SourceReferences to plugins This allows the user to clone and checkout the source code of CDT without knowing where the repository is. See: https://wiki.eclipse.org/PDE/UI/SourceReferences One use case is to right-click on a plug-in under the Plug-in dependencies in Package Explorer view and select Import from Repository. Note that for this EGit needs to be installed. What this patch does is to let Tycho generate the source references in the MANIFEST.MF of the built jars. So to test this patch, one can build the update site locally and inspect the manifests of the (non-source) jars. Change-Id: I807cd7842e3485ae1affcaa03ae08bdbb1677c97 Signed-off-by: Marc-Andre Laperle <marc-andre.laperle@ericsson.com> Reviewed-on: https://git.eclipse.org/r/39549 Tested-by: Hudson CI Reviewed-by: Alvaro Sanchez-Leon <alvsan09@gmail.com> Tested-by: Alvaro Sanchez-Leon <alvsan09@gmail.com>
2015-01-14 05:18:44 +01:00
</plugin>
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 22:22:23 +01:00
<plugin>
<groupId>org.eclipse.tycho</groupId>
<artifactId>tycho-surefire-plugin</artifactId>
<version>${tycho-version}</version>
<configuration>
<!-- Default configuration, UI tests may have to override these -->
<useUIHarness>false</useUIHarness>
<useUIThread>false</useUIThread>
<dependencies>
<dependency>
<type>p2-installable-unit</type>
<artifactId>org.eclipse.platform.feature.group</artifactId>
</dependency>
</dependencies>
<product>org.eclipse.platform.ide</product>
<argLine>${tycho.testArgLine} ${base.test.vmargs}</argLine>
Move the disable intro ini out of root of repo The root files in GitHub are a bit more prominent, so keep that area clean and move this special ini to a subdir. Change-Id: I12d95727e9dad29ebe4f50d47faa9e98753a52bc
2022-06-26 18:22:45 +02:00
<appArgLine>-pluginCustomization ${basedir}/../../releng/disable_intro_in_tests.ini</appArgLine>
Bug 499777: Don't fail build if no tests are found using tags can cause all tests to be excluded, which is ok and should not fail the build Change-Id: Ia7f5e06c6bfb76df0cd3ac7b5ffe13e555489fad
2021-04-06 23:01:55 +02:00
<!-- using tags can cause all tests to be excluded, which is ok and should not fail the build -->
<failIfNoTests>false</failIfNoTests>
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 22:22:23 +01:00
</configuration>
</plugin>
[releng] Update comparator repo Change-Id: Ib7628c0b68a2392c7975019f5dcb74fa4ade2274
2018-12-19 21:10:31 +01:00
<plugin>
<groupId>org.eclipse.tycho</groupId>
<artifactId>tycho-p2-plugin</artifactId>
<version>${tycho-version}</version>
[releng] Try to fix signing with baseline replacement Change-Id: I1b1b63e095c9309836ec0850c7afe6adf09ebf51
2018-12-20 14:00:52 +01:00
<executions>
<execution>
<id>baselinereplace-p2-metadata</id>
<goals>
<goal>p2-metadata</goal>
</goals>
<phase>verify</phase>
Bug 547894: Baseline replace must happen after pack200 The configuration for baseline replacement needs to be split. This may be a bug in Tycho, but I cannot tell. It seems to me the configuration about ignoredPatterns should be read from the configuration block in the execution block, but it isn't. Change-Id: I35e3f4007b0afc21d8bd81d5b07f76581879bc76
2019-06-07 22:45:27 +02:00
<configuration>
Bug 547894: Provide a way to skip baseline replace and compare Change-Id: If8080db7374eabb7a640deba0fab1e26a785ac5c
2019-06-26 15:56:49 +02:00
<baselineMode>${replace-version-with-baselines.mode}</baselineMode>
<baselineReplace>${replace-version-with-baselines.replace}</baselineReplace>
Bug 547894: Baseline replace must happen after pack200 The configuration for baseline replacement needs to be split. This may be a bug in Tycho, but I cannot tell. It seems to me the configuration about ignoredPatterns should be read from the configuration block in the execution block, but it isn't. Change-Id: I35e3f4007b0afc21d8bd81d5b07f76581879bc76
2019-06-07 22:45:27 +02:00
<baselineRepositories>
<repository>
<url>${comparator.repo}</url>
</repository>
</baselineRepositories>
</configuration>
[releng] Try to fix signing with baseline replacement Change-Id: I1b1b63e095c9309836ec0850c7afe6adf09ebf51
2018-12-20 14:00:52 +01:00
</execution>
</executions>
Bug 547894: Fail build if differences before baseline replace Also fix version numbers in all bundles who's binary contents have changed despite no change in the source of the bundle. Change-Id: Ic67b79aafa801c7ce96c5e52843ad5c881827d84
2019-06-07 16:56:59 +02:00
<configuration>
<ignoredPatterns>
<pattern>META-INF/ECLIPSE_.RSA</pattern>
<pattern>META-INF/ECLIPSE_.SF</pattern>
Bug 558827: Add build id timestamp to features properly This was lost when the build system was moved to Maven/Tycho for CDT 8 and restores the information. Note that with the p2 baseline compare and replace this will show the build id of when the branding plugin (the one with the about.mappings) was built, which compared to the feature version may be older. The about.mappings, as it is generated on each build, is ignored from p2 compare and replace. Change-Id: I38d1fcc5f618d4037baa2c8b908952421c712fc6
2020-01-06 18:03:23 +01:00
<pattern>about.mappings</pattern>
[releng] Ignore Lucene generated index files when doing baseline replace Change-Id: I4702d75169634eb9d939b212b318d5656258e508
2019-06-11 17:46:22 +02:00
<pattern>index/*</pattern>
Bug 547894: Fail build if differences before baseline replace Also fix version numbers in all bundles who's binary contents have changed despite no change in the source of the bundle. Change-Id: Ic67b79aafa801c7ce96c5e52843ad5c881827d84
2019-06-07 16:56:59 +02:00
</ignoredPatterns>
</configuration>
[releng] Update comparator repo Change-Id: Ib7628c0b68a2392c7975019f5dcb74fa4ade2274
2018-12-19 21:10:31 +01:00
</plugin>
Mavenizing CDT releng. Also removed unsupported cdt.core fragments from the platform feature.
2011-06-28 11:21:58 +02:00
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-resources-plugin</artifactId>
Update maven plugins maven-enforcer-plugin 3.2.1 -> 3.4.1 maven-pmd-plugin 3.20.0 -> 3.21.2 maven-resources-plugin 3.3.0 -> 3.3.1 org.codehaus.mojo:build-helper-maven-plugin 3.4.0 -> 3.5.0 org.codehaus.mojo:sonar-maven-plugin 2.4 -> 3.10.0.2594 org.jacoco:jacoco-maven-plugin 0.8.8 -> 0.8.11
2024-02-21 16:09:40 +01:00
<version>3.3.1</version>
Mavenizing CDT releng. Also removed unsupported cdt.core fragments from the platform feature.
2011-06-28 11:21:58 +02:00
<configuration>
<encoding>ISO-8859-1</encoding>
</configuration>
</plugin>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-antrun-plugin</artifactId>
Update versions of maven plugins Part of #320
2023-03-13 19:20:50 +01:00
<version>3.1.0</version>
Mavenizing CDT releng. Also removed unsupported cdt.core fragments from the platform feature.
2011-06-28 11:21:58 +02:00
</plugin>
Unify maven-compiler-plugin setting Define the common version in parent pom and don't override it. Move to latest version while at it.
2024-02-21 15:25:23 +01:00
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-compiler-plugin</artifactId>
<version>3.12.1</version>
</plugin>
Mavenizing CDT releng. Also removed unsupported cdt.core fragments from the platform feature.
2011-06-28 11:21:58 +02:00
<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>findbugs-maven-plugin</artifactId>
[releng] update maven dependency versions Change-Id: Id55ef378ed1abf4a71f31ef27b08c3b59be05317
2018-03-19 11:36:23 +01:00
<version>3.0.5</version>
Mavenizing CDT releng. Also removed unsupported cdt.core fragments from the platform feature.
2011-06-28 11:21:58 +02:00
<configuration>
Allow for filtering of findbugs Choose version 2.5.2 which is what is supported by CDT's HIPP. Note that by removing the version altogether, the latest available findBugs would be selected. However, this could lead to different results between manual builds and HIPP builds, which is why I thought it would be better to specify the version explicitly. FindBugs can be run by adding the string findbugs:findbugs as a maven parameter, either in a local maven build, or on HIPP. Add releng/findbugs-exclude.xml to control the errors shown by FindBugs. The content of that file was copied from the TM project, but should eventually be ajusted for CDT. Change-Id: Ibc8348b9286f00580a4079a7ca3c669708bc6194 Signed-off-by: Marc Khouzam <marc.khouzam@ericsson.com>
2015-02-04 19:26:47 +01:00
<xmlOutput>true</xmlOutput>
<excludeFilterFile>releng/findbugs-exclude.xml</excludeFilterFile>
Mavenizing CDT releng. Also removed unsupported cdt.core fragments from the platform feature.
2011-06-28 11:21:58 +02:00
<failOnError>false</failOnError>
</configuration>
<executions>
<execution>
<goals>
<goal>check</goal>
</goals>
</execution>
</executions>
</plugin>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-pmd-plugin</artifactId>
Update maven plugins maven-enforcer-plugin 3.2.1 -> 3.4.1 maven-pmd-plugin 3.20.0 -> 3.21.2 maven-resources-plugin 3.3.0 -> 3.3.1 org.codehaus.mojo:build-helper-maven-plugin 3.4.0 -> 3.5.0 org.codehaus.mojo:sonar-maven-plugin 2.4 -> 3.10.0.2594 org.jacoco:jacoco-maven-plugin 0.8.8 -> 0.8.11
2024-02-21 16:09:40 +01:00
<version>3.21.2</version>
Mavenizing CDT releng. Also removed unsupported cdt.core fragments from the platform feature.
2011-06-28 11:21:58 +02:00
<configuration>
Clean up Maven build (#662) * remove invalid tycho resolver config (not valid since many versions) * fix PMD plugin configuration (config attribute was renamed in 3.18) * remove duplicate versions already managed in pluginManagement section * fix indentation * move all not yet configured versions into pluginManagement of the parent module to avoid further duplication * consume the target platform as file, not as maven artifact (this simplifies building a single module A LOT) * remove invalid tycho-source-plugin configuration * disable tycho consumer POM generation (not needed here, and avoids a warning in each module) * remove prerequisites. that's for maven plugins only, and this POM already contains the better suited similar maven enforcer rule * enforce UTF-8 for javadoc generation (the build fails on Windows otherwise, trying to read some Japanese? characters with the Windows default encoding)
2023-12-28 20:35:58 +01:00
<inputEncoding>utf-8</inputEncoding>
Mavenizing CDT releng. Also removed unsupported cdt.core fragments from the platform feature.
2011-06-28 11:21:58 +02:00
<minimumTokens>100</minimumTokens>
Bug 562494: Update BREE to Java 11 Change-Id: I0c91aafc0cb1b179936acbd4c9df2d961899e3fa
2020-08-23 14:05:03 +02:00
<targetJdk>11</targetJdk>
Mavenizing CDT releng. Also removed unsupported cdt.core fragments from the platform feature.
2011-06-28 11:21:58 +02:00
<format>xml</format>
<failOnViolation>false</failOnViolation>
</configuration>
<executions>
<execution>
<goals>
<goal>cpd-check</goal>
</goals>
</execution>
</executions>
</plugin>
Use Tycho 0.17 for build. This also required to add configuration for eclipserun plugin in the master pom. Change-Id: Id9814096a6ee430058470a8eefd6c18d1f90bebd Reviewed-on: https://git.eclipse.org/r/12773 Reviewed-by: Marc-Andre Laperle <marc-andre.laperle@ericsson.com> IP-Clean: Marc-Andre Laperle <marc-andre.laperle@ericsson.com> Tested-by: Marc-Andre Laperle <marc-andre.laperle@ericsson.com>
2013-05-14 11:37:44 +02:00
<plugin>
Clean up Maven build (#662) * remove invalid tycho resolver config (not valid since many versions) * fix PMD plugin configuration (config attribute was renamed in 3.18) * remove duplicate versions already managed in pluginManagement section * fix indentation * move all not yet configured versions into pluginManagement of the parent module to avoid further duplication * consume the target platform as file, not as maven artifact (this simplifies building a single module A LOT) * remove invalid tycho-source-plugin configuration * disable tycho consumer POM generation (not needed here, and avoids a warning in each module) * remove prerequisites. that's for maven plugins only, and this POM already contains the better suited similar maven enforcer rule * enforce UTF-8 for javadoc generation (the build fails on Windows otherwise, trying to read some Japanese? characters with the Windows default encoding)
2023-12-28 20:35:58 +01:00
<groupId>org.eclipse.tycho.extras</groupId>
<artifactId>tycho-eclipserun-plugin</artifactId>
<version>${tycho-version}</version>
<configuration>
<applicationArgs>
<arg>-application</arg>
<arg>org.eclipse.ant.core.antRunner</arg>
<arg>-buildfile</arg>
<arg>customBuildCallbacks.xml</arg>
<arg>build.index</arg>
</applicationArgs>
<dependencies>
<dependency>
<artifactId>org.apache.ant</artifactId>
<type>eclipse-plugin</type>
</dependency>
<dependency>
<artifactId>org.eclipse.help.base</artifactId>
<type>eclipse-plugin</type>
</dependency>
<dependency>
<artifactId>org.eclipse.ant.core</artifactId>
<type>eclipse-plugin</type>
</dependency>
</dependencies>
<!-- This needs to be explicitely set now, see https://bugs.eclipse.org/bugs/show_bug.cgi?id=395281 -->
<repositories>
<repository>
<id>platform</id>
<layout>p2</layout>
<url>${help-docs-eclipserun-repo}</url>
</repository>
</repositories>
</configuration>
<executions>
<execution>
<goals>
<goal>eclipse-run</goal>
</goals>
<phase>compile</phase>
<configuration>
[#657] CDT cannot be built on Java 21 due to security manager changes * Switch CI to Java 21 * Remove config generation for debug application * Remove `org.eclipse.osgi.services` from `proxy.server` product * Remove `org.eclipse.osgi.services` from `org.eclipse.cdt.debug.application.product` product * Move `org.eclipse.cdt.debug.application.product` from profile to general part Signed-off-by: Alexander Fedorov <alexander.fedorov@arsysop.ru>
2024-04-19 17:21:37 +02:00
<executionEnvironment>JavaSE-21</executionEnvironment>
Clean up Maven build (#662) * remove invalid tycho resolver config (not valid since many versions) * fix PMD plugin configuration (config attribute was renamed in 3.18) * remove duplicate versions already managed in pluginManagement section * fix indentation * move all not yet configured versions into pluginManagement of the parent module to avoid further duplication * consume the target platform as file, not as maven artifact (this simplifies building a single module A LOT) * remove invalid tycho-source-plugin configuration * disable tycho consumer POM generation (not needed here, and avoids a warning in each module) * remove prerequisites. that's for maven plugins only, and this POM already contains the better suited similar maven enforcer rule * enforce UTF-8 for javadoc generation (the build fails on Windows otherwise, trying to read some Japanese? characters with the Windows default encoding)
2023-12-28 20:35:58 +01:00
</configuration>
</execution>
</executions>
</plugin>
<plugin>
<groupId>org.eclipse.tycho</groupId>
<artifactId>tycho-gpg-plugin</artifactId>
<version>${tycho-version}</version>
<executions>
<execution>
<id>pgpsigner</id>
<goals>
<goal>sign-p2-artifacts</goal>
</goals>
<configuration>
<keyname>4F23165B6AC51B15</keyname>
<skipIfJarsigned>false</skipIfJarsigned>
</configuration>
</execution>
</executions>
</plugin>
<plugin>
<groupId>org.eclipse.tycho.extras</groupId>
<artifactId>tycho-document-bundle-plugin</artifactId>
<version>${tycho-version}</version>
<configuration>
<javadocOptions>
<encoding>UTF-8</encoding>
</javadocOptions>
</configuration>
</plugin>
<plugin>
<groupId>org.eclipse.tycho</groupId>
<artifactId>tycho-p2-director-plugin</artifactId>
<version>${tycho-version}</version>
</plugin>
<plugin>
<groupId>org.eclipse.tycho</groupId>
<artifactId>tycho-p2-repository-plugin</artifactId>
<version>${tycho-version}</version>
</plugin>
<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>build-helper-maven-plugin</artifactId>
Update maven plugins maven-enforcer-plugin 3.2.1 -> 3.4.1 maven-pmd-plugin 3.20.0 -> 3.21.2 maven-resources-plugin 3.3.0 -> 3.3.1 org.codehaus.mojo:build-helper-maven-plugin 3.4.0 -> 3.5.0 org.codehaus.mojo:sonar-maven-plugin 2.4 -> 3.10.0.2594 org.jacoco:jacoco-maven-plugin 0.8.8 -> 0.8.11
2024-02-21 16:09:40 +01:00
<version>3.5.0</version>
Clean up Maven build (#662) * remove invalid tycho resolver config (not valid since many versions) * fix PMD plugin configuration (config attribute was renamed in 3.18) * remove duplicate versions already managed in pluginManagement section * fix indentation * move all not yet configured versions into pluginManagement of the parent module to avoid further duplication * consume the target platform as file, not as maven artifact (this simplifies building a single module A LOT) * remove invalid tycho-source-plugin configuration * disable tycho consumer POM generation (not needed here, and avoids a warning in each module) * remove prerequisites. that's for maven plugins only, and this POM already contains the better suited similar maven enforcer rule * enforce UTF-8 for javadoc generation (the build fails on Windows otherwise, trying to read some Japanese? characters with the Windows default encoding)
2023-12-28 20:35:58 +01:00
</plugin>
Mavenizing CDT releng. Also removed unsupported cdt.core fragments from the platform feature.
2011-06-28 11:21:58 +02:00
</plugins>
</pluginManagement>
</build>
</project>
Reference in a new issue Copy permalink