Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "EMF DiffMerge/BuildConfiguration"
| Line 5: | Line 5: | ||
== Project stucture == | == Project stucture == | ||
| − | The contents from the project are available in | + | The contents from the project are available in [http://git.eclipse.org/c/diffmerge/ four different repositories], each following a similar structure: |
| − | Given that both | + | Given that both the coevolution, patch and patterns repository depends on the core repository, the corresponding jobs have to be set up as follows: |
| − | * A CI update site created by the core repository is made available to the other builds using the Maven property | + | * A CI update site created by the core repository is made available to the other builds using the Maven property [http://git.eclipse.org/c/diffmerge/org.eclipse.emf.diffmerge.coevolution.git/tree/releng/org.eclipse.emf.diffmerge.coevolution.configuration/pom.xml#n13 core.repo.url]. This can be set up correctly by the build on hudson. |
| − | * The | + | * The Co-Evolution, Patch and Patterns builds are also triggered each time the Core project builds. |
== Adding a new project to the build == | == Adding a new project to the build == | ||
Latest revision as of 06:05, 20 March 2017
Contents
Build concepts
EMF Diff/Merge uses Maven Tycho for its build. In order to minimize required build descriptors, it relies on the pom-less builds feature available from Tycho 0.24. It is important to note that this means Maven version 3.3 is required to execute these builds.
Project stucture
The contents from the project are available in four different repositories, each following a similar structure:
Given that both the coevolution, patch and patterns repository depends on the core repository, the corresponding jobs have to be set up as follows:
- A CI update site created by the core repository is made available to the other builds using the Maven property core.repo.url. This can be set up correctly by the build on hudson.
- The Co-Evolution, Patch and Patterns builds are also triggered each time the Core project builds.