Summary

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

Details

Page properties

Author

...	...	@@ -1,1 +1,1 @@
1		-XWiki.mkr
	1	+XWiki.tig

Content

...	...	@@ -29,7 +29,7 @@
29	29	== Project Settings ==
30	30
31	31	* //Java Build Path//
32		-** On the //Libraries// tab, remove the default JRE System Library and click //Add Library//. Choose //JRE System Library// and click //Next//. Select //Execution environment//, ensure that Workspace defualt JRE is //jdk1.8.0//.
	32	+** On the //Libraries// tab, remove the default JRE System Library and click //Add Library//. Choose //JRE System Library// and click //Next//. Select //Execution environment//, select the one beginning with //J2SE-1.5// and click //Finish//.
33	33	* //Checkstyle//
34	34	** If your plug-in only contains generated code, disable Checkstyle.
35	35	** Otherwise, activate Checkstyle.
...	...	@@ -103,9 +103,8 @@
103	103
104	104	== Automatic Build Integration ==
105	105
106		-* (((
107		-New plugin
108		-* (((
	106	+* New plugin\\
	107	+** (((
109	109	New plugins need a {{code language="none"}}pom.xml{{/code}} in the plugin's root folder
110	110
111	111	{{code title="plugin pom.xml" language="html/xml" collapse="true"}}
...	...	@@ -127,13 +127,12 @@
127	127
128	128	{{/code}}
129	129	)))
130		-* Make sure that {{code language="none"}}<version>{{/code}} is in sync with {{code language="none"}}Bundle-Version{{/code}} in {{code language="none"}}META-INF/MANIFEST.MF{{/code}}
131		-* Add a {{code language="none"}}<module>{{/code}} entry in the corresponding parent POM i.e. {{code language="none"}}plugins/pom.xml{{/code}}
132		-* (((
133		-If your plugin uses xtend, tell maven to run the xtend compiler in {{code language="none"}}pom.xml{{/code}}(% style="font-family: monospace;" %)
	129	+** Make sure that {{code language="none"}}<version>{{/code}} is in sync with {{code language="none"}}Bundle-Version{{/code}} in {{code language="none"}}META-INF/MANIFEST.MF{{/code}}
	130	+** Add a {{code language="none"}}<module>{{/code}} entry in the corresponding parent POM i.e. {{code language="none"}}plugins/pom.xml{{/code}}
	131	+** If your plugin uses xtend, tell maven to run the xtend compiler in {{code language="none"}}pom.xml{{/code}}(% style="font-family: monospace;" %)
134	134
135	135
136		-{{code language="html/xml" collapse="true"}}
	134	+{{code}}
137	137	<build>
138	138	<sourceDirectory>src</sourceDirectory>
139	139	<plugins>
...	...	@@ -153,14 +153,11 @@
153	153
154	154
155	155	{{/code}}
156		-)))
157		-)))
158		-* New JUnit test plugin\\
159		-** Basically the same steps as for plugins except {{code language="none"}}<packaging>{{/code}} is {{code language="none"}}eclipse-test-plugin{{/code}}
160		-* New features\\
161		-** The same steps as for plugins except {{code language="none"}}<packaging>{{/code}} is {{code language="none"}}eclipse-feature{{/code}}
162		-** Additionally if sources are to be distributed a separate source feature with the corresponding source-bundles must be created
163	163
	155	+{{warning}}
	156	+This section hasn't been written yet.
	157	+{{/warning}}
	158	+
164	164	= Features =
165	165
166	166	== Naming Conventions ==

Confluence.Code.ConfluencePageClass[0]

Id

...	...	@@ -1,1 +1,1 @@
1		-13762621
	1	+1540139

URL

...	...	@@ -1,1 +1,1 @@
1		-https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/KIELER/pages/13762621/Naming and Metadata
	1	+https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/KIELER/pages/1540139/Naming and Metadata