<
From version < 4.1 >
edited by cds
on 2012/04/03 18:04
To version < 7.1 >
edited by tig
on 2012/05/24 13:25
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.cds
1 +XWiki.tig
Content
... ... @@ -103,10 +103,64 @@
103 103  
104 104  == Automatic Build Integration ==
105 105  
106 -{{warning}}
107 -This section hasn't been written yet.
108 -{{/warning}}
106 +* (((
107 +New plugin
108 +* (((
109 +New plugins need a {{code language="none"}}pom.xml{{/code}} in the plugin's root folder
109 109  
111 +{{code title="plugin pom.xml" language="html/xml" collapse="true"}}
112 + <?xml version="1.0" encoding="UTF-8"?>
113 +<project xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd" xmlns="http://maven.apache.org/POM/4.0.0"
114 + xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
115 + <modelVersion>4.0.0</modelVersion>
116 + <parent>
117 + <groupId>de.cau.cs.kieler</groupId>
118 + <artifactId>plugins</artifactId>
119 + <version>0.0.1-SNAPSHOT</version>
120 + </parent>
121 + <groupId>de.cau.cs.kieler</groupId>
122 + <artifactId>YOUR.NEW.PLUGIN.NAME</artifactId>
123 + <version>0.7.0-SNAPSHOT</version>
124 + <packaging>eclipse-plugin</packaging>
125 +</project>
126 +
127 +
128 +{{/code}}
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;" %)
134 +
135 +
136 +{{code language="html/xml" collapse="true"}}
137 + <build>
138 + <sourceDirectory>src</sourceDirectory>
139 + <plugins>
140 + <plugin>
141 + <groupId>org.eclipse.xtend2</groupId>
142 + <artifactId>xtend-maven-plugin</artifactId>
143 + <executions>
144 + <execution>
145 + <goals>
146 + <goal>compile</goal>
147 + </goals>
148 + </execution>
149 + </executions>
150 + </plugin>
151 + </plugins>
152 + </build>
153 +
154 +
155 +{{/code}}
156 +)))
157 +)))
158 +* New JUnit test plugin\\
159 +** Basically the same steps as for plugins except <packaging> is eclipse-test-plugin
160 +* New features
161 +** The same steps as for plugins except <packaging> is eclipse-feature
162 +** Additionally if sources are to be distributed a separate source-feature with the corresponding source-bundles must be created
163 +
110 110  = Features =
111 111  
112 112  == Naming Conventions ==
Confluence.Code.ConfluencePageClass[0]
Id
... ... @@ -1,1 +1,1 @@
1 -1540133
1 +1540141
URL
... ... @@ -1,1 +1,1 @@
1 -https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/KIELER/pages/1540133/Naming and Metadata
1 +https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/KIELER/pages/1540141/Naming and Metadata