Page History

...

New plugin

New plugins need a pom.xml in the plugin's root folder

Code Block

language	html/xml
title	plugin pom.xml
collapse	true

 <?xml version="1.0" encoding="UTF-8"?>
<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"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
  <modelVersion>4.0.0</modelVersion>
  <parent>
    <groupId>de.cau.cs.kieler</groupId>
    <artifactId>plugins</artifactId>
    <version>0.0.1-SNAPSHOT</version>
  </parent>
  <groupId>de.cau.cs.kieler</groupId>
  <artifactId>YOUR.NEW.PLUGIN.NAME</artifactId>
  <version>0.7.0-SNAPSHOT</version>
  <packaging>eclipse-plugin</packaging>
</project>

Make sure that <version> is in sync with Bundle-Version in META-INF/MANIFEST.MF
Add a <module> entry in the corresponding parent POM i.e. plugins/pom.xml

If your plugin uses xtend, tell maven to run the xtend compiler in pom.xml

Code Block

language	html/xml
collapse	true

  <build>
    <sourceDirectory>src</sourceDirectory>
    <plugins>
      <plugin>
        <groupId>org.eclipse.xtend2</groupId>
        <artifactId>xtend-maven-plugin</artifactId>
        <executions>
          <execution>
            <goals>
              <goal>compile</goal>
            </goals>
          </execution>
        </executions>
      </plugin>
    </plugins>
  </build>

New JUnit test plugin
- Basically the same steps as for plugins except <packaging> is eclipse-test-plugin
New features
- The same steps as for plugins except <packaging> is eclipse-feature
- Additionally if sources are to be distributed a separate source - feature with the corresponding source-bundles must be created

...

Page tree

Versions Compared

Old Version 6

New Version 7

Key