This profile can only be run on the CDT CI machinesĪs access to Eclipse key signing server is needed to sign the jars. will not run with mvn package even if profile is specified. Requires verify phase of maven to run, i.e. To do that run with the baseline-compare-and-replace profile. If you have the same version of Java as the build machine you can run baseline comparison and On a local build you want to avoid baseline replace and compare,Įspecially if you have different versions of Java than the baseline was built with. See baseline-compare-and-replaceīaseline-compare-and-replace profile controls whether baseline replace and compare Uses this to speedup turnaround on changes only affecting the terminal. A special terminal only p2 site is created in terminal/repo/target/repository. Running maven like this mvn -f terminal/pom.xml verify -P only-terminal to build and test only the terminalĪnd its dependencies. The terminal directory has a special profile that enables only the terminal and its dependencies when used. The CI build uses this to parallelize tests. Using any of the above profiles can skip large sets of tests. In debug/.application.product skip-all-tests, skip-tests-except-cdt-ui, skip-tests-except-dsf-gdb, skip-tests-except-lsp, skip-tests-except-cdt-other Using the build-standalone-debugger-rcp profile will include the standalone debugger, located
Successfully and for rebuilding non-Java parts of CDT are much more extensive than standard Maven & Java and include The Dockerfiles used for CDT's images are To build CDT plug-ins you need a standard Maven & Java developement environment. The current set of options to Maven used for building on the CI can be seen in the Jenkinsfiles
And the resulting p2 repository will be in releng//target/repository
0 kommentar(er)
