Summary

• Page properties (1 modified, 0 added, 0 removed)
• Objects (1 modified, 0 added, 0 removed)
  • Confluence.Code.ConfluencePageClass[0]

Details

Page properties

Content

...	...	@@ -36,39 +36,33 @@
36	36
37	37	=== POM Files ===
38	38
39		-The basic structure of the POM files can be seen below:
	39	+The basic structure of the POM files is the same for both, the pragmatics and semantics repository, and can be seen below:
40	40
41	41	[[image:attach:pomfiles.png]]
42	42
43		-Each plug-in and feature has a corresponding (usually rather small) POM file. The POM files in the {{code language="none"}}features{{/code}} and {{code language="none"}}plugins{{/code}} directories know about the different features and plug-ins. The parent POM file, which all other POM files copy basic configuration from, knows about the feature and plug-in POM files. In addition, the {{code language="none"}}build{{/code}} directory also contains a bunch of subdirectories. These also contain POM files specialized for building the P2 repositories necessary to publish our Eclipse features.
	43	+Each plug-in and feature has a corresponding (usually rather small) POM file. The POM files in the {{code language="none"}}features{{/code}} and {{code language="none"}}plugins{{/code}} directories know about the different features and plug-ins. The parent POM file, which all other POM files copy basic configuration from, knows about the feature and plug-in POM files, as well as about every kind of build configuration we have (for building the pragmatics repository, for building the KWebS product, etc.). In addition, the {{code language="none"}}build{{/code}} directory also contains a bunch of subdirectories housing POM files that produce our p2 repositories and our products.
44	44
45	45	=== Using the KIELER Maven Build ===
46	46
47		-Using the KIELER Maven build requires knowledge about two aspects: necessary configuration / required libraries and invoking Maven.
	47	+Using the KIELER Maven build requires two things: a working Maven installation (d'oh...) and knowledge about how exactly to trigger a build. We leave the former to you, but the latter is what this section is about.
48	48
49		-==== Necessary Configuration ====
	49	+To actually build KIELER, navigate to the {{code language="none"}}/build/{{/code}} directory and run the following command line:
50	50
51		-KIELER needs to be built against a P2 repository generated from our Eclipse reference installation. The path to this repository is found in the parent POM file and must be changed if the repository location changes. Also, when changing the reference installation, the repository has to be updated using the following magic command (adapted accordingly):
52		-
53	53	{{code language="none"}}
54		-java -jar eclipse_3.8/plugins/org.eclipse.equinox.launcher_*.jar \
55		--application org.eclipse.equinox.p2.publisher.FeaturesAndBundlesPublisher \
56		--metadataRepository file:/home/java/repository/juno382 \
57		--artifactRepository file:/home/java/repository/juno382 \
58		--source /home/java/eclipse_3.8/ \
59		--publishArtifacts
	52	+. /home/java/java-env # Only necessary when working on our servers
	53	+mvn clean package -P <profile>
60	60	{{/code}}
61	61
62		-==== Invoking Maven ====
	56	+Once Maven has finished, the different build artifacts may be found in the {{code language="none"}}/build/de.cau.cs.kieler.<profile>.repository/target{{/code}} directories. The following build profiles are available in the KIELER Pragmatics repository:
63	63
64		-To actually build KIELER once all preliminaries are done, navigate to the {{code language="none"}}/build/de.cau.cs.kieler.parent{{/code}} directory and run the following command line:
	58	+* klighdning – Builds a standalone version of the KLighDning server, based on the current nightly pragmatics update site.
	59	+* kwebs – Builds a standalone version of the KWebS server, based on the current nightly pragmatics update site.
	60	+* pragmatics – Builds a p2 repository that contains our pragmatics features. This is what would usually be pushed online for people to download as our nightly pragmatics build.
	61	+* ptolemy-rcp – Produces a standalone version of our Ptolemy Model Viewer, based on the current nightly build pragmatics update site.
65	65
66		-{{code language="none"}}
67		-. /home/java/java-env # Only necessary when working on our servers
68		-mvn clean package -P <profile> # For a list of available profiles, see parent pom.xml
69		-{{/code}}
	63	+The following build profiles are available in the KIELER Semantics repository:
70	70
71		-Once Maven has finished, the different build artifacts may be found in the {{code language="none"}}/build/de.cau.cs.kieler.*.repository/target{{/code}} directories.
	65	+* TODO: Add build profiles.
72	72
73	73	=== What to Be Aware of ===
74	74
...	...	@@ -81,15 +81,22 @@
81	81
82	82	We distribute our KLay layout algorithms in two library files: one that contains just our algorithms, and another one that also contains dependencies such as required EMF classes. To build the KLay libraries, navigate to the {{code language="none"}}/build/de.cau.cs.kieler.klay.libraries{{/code}} directory and do the following:
83	83
84		-1. Set the {{code language="none"}}PRODUCT{{/code}} environment variable to point to a complete installation of KIELER. You can get one by using the automatic Maven build.
	78	+1. Set the TARGET_PLATFORM environment variable to point to a local copy of our currently used target platform p2 repository. Ask {{mention reference="XWiki.cds" style="FULL_NAME" anchor="XWiki-cds-BDGaI"/}} where you can get that.
	79	+1. Set the {{code language="none"}}KIELER_REPOSITORY{{/code}} environment variable to point to a local copy of a p2 repository of our pragmatics build. Again, ask {{mention reference="XWiki.cds" style="FULL_NAME" anchor="XWiki-cds-eBnpF"/}} where you can get that.
85	85	1. Run Ant on the {{code language="none"}}build.xml{{/code}} file. This will produce both versions of the KLay layout library.
86	86
	82	+{{note}}
	83	+We would love to switch our KLay library build over to Maven since that would allow us to publish the library in an official Maven artifact repository.
	84	+{{/note}}
	85	+
	86	+
	87	+
87	87	== Continuous and Nightly Builds ==
88	88
89		-There are basically three different build plans for each of the KIELER projects:
	90	+There are basically four different kinds of build plans for each of the KIELER projects:
90	90
91		-1. **Continuous Plugins** – Compiles the plug-ins and runs the unit tests on them. None of the compiled artifacts are published anywhere. This plan is triggered by pushing stuff into the repositories, giving early feedback regarding whether committed changes break anything.
92		-1. **Nightly Product** – Compiles the plug-ins and assembles distributable product files and update sites. Distributable files are published in the nightly build directory {{code language="none"}}/home/kieler/public_html/files/nightly{{/code}}. Update sites are published in {{code language="none"}}/home/kieler/public_html/updatesite/nightly{{/code}}. This plan is run once every night.
	92	+1. **Continuous Plugins** – Compiles the plug-ins and runs the unit tests on them. None of the compiled artifacts are published anywhere (in fact, no update site or product is even produced). This plan is triggered by pushing stuff into the repositories, giving early feedback regarding whether committed changes break anything.
	93	+1. **Nightly <Product>** – Assembles distributable product files and/or update sites. Distributable files are published in the nightly build directory {{code language="none"}}/home/kieler/public_html/files/nightly{{/code}}. Update sites are published in {{code language="none"}}/home/kieler/public_html/updatesite/nightly{{/code}}. These plans are run once every night.
93	93	1. **Nightly Rating** – Compiles the plug-ins and runs our code quality rating doclet on them. The result is a website published at {{code language="none"}}/home/kieler/public_html/rating{{/code}}. This plan is run once every night.
94	94	1. **Release Builds** – Continuous builds of release branches once a release is imminent. These usually run whenever changes are pushed into the repository.
95	95
...	...	@@ -122,13 +122,33 @@
122	122	...klay.libraries/build.xml
123	123	{{/code}}
124	124	)))|(((
125		-KIELER Pragmatics -> Nightly Product
	126	+KIELER Pragmatics -> Nightly KLay
126	126	)))|(% colspan="1" %)(% colspan="1" %)
127	127	(((
128	128	{{code language="none"}}
129		-/home/kieler/public_html/files/nightly/
	130	+/home/kieler/public_html/files/nightly/klay
130	130	{{/code}}
131	131	)))
	133	+|(% colspan="1" %)(% colspan="1" %)
	134	+(((
	135	+KLighDning RCA
	136	+)))|(% colspan="1" %)(% colspan="1" %)
	137	+(((
	138	+Pragmatics
	139	+)))|(% colspan="1" %)(% colspan="1" %)
	140	+(((
	141	+{{code language="none"}}
	142	+...klighdning.repository/pom.xml
	143	+{{/code}}
	144	+)))|(% colspan="1" %)(% colspan="1" %)
	145	+(((
	146	+KIELER Pragmatics -> Nightly KLighDning
	147	+)))|(% colspan="1" %)(% colspan="1" %)
	148	+(((
	149	+{{code language="none"}}
	150	+/home/kieler/public_html/files/nightly/klighning
	151	+{{/code}}
	152	+)))
132	132	|(((
133	133	KWebS RCA
134	134	)))|(((
...	...	@@ -142,7 +142,7 @@
142	142	)))|(% colspan="1" %)(% colspan="1" %)
143	143	(((
144	144	{{code language="none"}}
145		-/home/kieler/public_html/files/nightly/
	166	+/home/kieler/public_html/files/nightly/kwebs
146	146	{{/code}}
147	147	)))
148	148	|(((

Confluence.Code.ConfluencePageClass[0]

Id

...	...	@@ -1,1 +1,1 @@
1		-6160516
	1	+8650846

URL

...	...	@@ -1,1 +1,1 @@
1		-https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/KIELER/pages/6160516/Build Management
	1	+https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/KIELER/pages/8650846/Build Management