Summary

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

Details

Page properties

Content

...	...	@@ -8,7 +8,7 @@
8	8
9	9
10	10
11		-{{toc/}}
	11	+{{toc minLevel="2"/}}
12	12
13	13	== Software We Use ==
14	14
...	...	@@ -48,17 +48,8 @@
48	48
49	49	==== Necessary Configuration ====
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):
	51	+KIELER needs to be built against a P2 repository generated from an Eclipse reference installation. The command for doing that is described on [[this page>>doc:Eclipse Server Installation]]. You may need to adapt the reference repository location in the parent POM files.
52	52
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
60		-{{/code}}
61		-
62	62	==== Invoking Maven ====
63	63
64	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:

Confluence.Code.ConfluencePageClass[0]

Id

...	...	@@ -1,1 +1,1 @@
1		-6160425
	1	+7701008

URL

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