Summary

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

Details

Page properties

Content

...	...	@@ -62,7 +62,9 @@
62	62
63	63	The following build profiles are available in the KIELER Semantics repository:
64	64
65		-* TODO: Add build profiles.
	65	+{{warning title="ToDo"}}
	66	+Document the Semantics build profiles.
	67	+{{/warning}}
66	66
67	67	=== What to Be Aware of ===
68	68
...	...	@@ -75,8 +75,8 @@
75	75
76	76	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:
77	77
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-CeanB"/}} 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-shyrQ"/}} where you can get that.
	80	+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-daTra"/}} where you can get that.
	81	+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-vKzxD"/}} where you can get that.
80	80	1. Run Ant on the {{code language="none"}}build.xml{{/code}} file. This will produce both versions of the KLay layout library.
81	81
82	82	{{note}}
...	...	@@ -102,6 +102,10 @@
102	102
103	103	Our automatic builds produce a bunch of so-called //artifacts//: redistributable applications as well as a number of update sites. This table lists all artifacts, the project or repository they belong to, the build file responsible for producing them, the Bamboo build plan that builds them, and the directory they are finally placed in.
104	104
	107	+{{tip title="Timestamps"}}
	108	+Don't be alarmed if the timestamps of the plugin and feature jar files on the updatesite don't match the current time. The time is probably UTC. Which is nice.
	109	+{{/tip}}
	110	+
105	105	|=(((
106	106	Artifact
107	107	)))|=(((

Confluence.Code.ConfluencePageClass[0]

Id

...	...	@@ -1,1 +1,1 @@
1		-8651454
	1	+42729514

URL

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