Summary

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

Details

Page properties

Content

...	...	@@ -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-kSYXs"/}} 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-ikrNl"/}} where you can get that.
	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-vTIPm"/}} 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-rdIHp"/}} 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}}
...	...	@@ -92,7 +92,7 @@
92	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	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.
94	94	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.
95		-1. **Release Builds** – Continuous builds of release branches once a release is imminent. These usually run whenever changes are pushed into the repository.
	95	+1. **Release Builds** – Continuous builds of release branches once a release is imminent. These usually run whenever changes are pushed into the repository. All release builds are placed in a special Bamboo project calles //KIELER Releases//.
96	96
97	97	The //Semantics// project has an additional build plan:
98	98

Confluence.Code.ConfluencePageClass[0]

Id

...	...	@@ -1,1 +1,1 @@
1		-8651034
	1	+8651036

URL

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