Copy Page

You are not logged in. Any changes you make will be marked as anonymous. You may want to Log In if you already have an account. You can also Sign Up for a new account.

<h1>Importing Maven projects in Eclipse</h1>

<p>See <a href="http://maven.apache.org/plugins/maven-eclipse-plugin/overview.html">Maven Eclipse Plugin</a></p>

<h1>Editing Maven projects in Eclipse</h1>

<p>See <a href="http://m2eclipse.codehaus.org/">Maven Eclipse Intregration</a></p>

<h1>Building Eclipse plugins in Maven</h1>

<p>Instructions targeting Eclipse 3.2, which uses OSGi bundles as plugin format.</p>

<p>The important files to have into account:</p>
<ul>
	<li>META-INF/MANIFEST.MF the OSGi manifest</li>
	<li>plugin.properties plugin config</li>
	<li>plugin.xml plugin config</li>
	<li>build.properties binaries and sources definition to build with PDE</li>
	<li>*<strong>*/*</strong>.jar dependent libraries, need to be in the source folder for building with PDE. They are packaged in the same folder in the zip. eg. if jars are in x/y they end in x/y folder of the jar, PDE doesn't allow changing it.</li>
</ul>

<p>Currently there are two integration points that overlap:</p>
<ul>
	<li><a href="http://maven.apache.org/plugins/maven-eclipse-plugin/overview.html">Maven Eclipse Plugin</a> generate manifest and enable PDE nature
	<ul>
		<li>Need a install plugins in eclipse workbench goal, installing the plugins as folders or jars</li>
	</ul>
	</li>
</ul>

<ul>
	<li><a href="http://cwiki.apache.org/FELIX/osgi-plugin-for-maven-2.html">Apache Felix OSGi plugin</a> can create an OSGi bundle, packaging dependencies, generating manifest,...
	<ul>
		<li>It always packages the dependencies, it'd need to allow setting Require-Bundle and not package some of them. If using provided scoped dependencies the transitive dependency part doesn't work. Right now it uses Import-Packages instead of Require-Bundle.</li>
		<li>would need to generate manifest and copy dependencies in working folder so PDE graphic tools can use the,</li>
	</ul>
	</li>
</ul>

<p>An OSGi bundle can be easily created with the Felix OSGi plugin. Integration between Maven and PDE is other story.</p>
<ul>
	<li>manifest needs to be in ${basedir}/META-INF/MANIFEST.MF</li>
	<li>jars need to be somewhere in ${basedir}</li>
	<li>other plugin dependencies must be either opened in eclipse or installed in the workspace</li>
</ul>

<p>This is a configuration that works</p>
<table class="wysiwyg-macro" data-macro-name="code" style="background-image: url(/plugins/servlet/confluence/placeholder/macro-heading?definition=e2NvZGV9&amp;locale=en_GB&amp;version=2); background-repeat: no-repeat;" data-macro-body-type="PLAIN_TEXT"><tr><td class="wysiwyg-macro-body"><pre>
&lt;build>
    &lt;resources>
      &lt;resource>
        &lt;directory>${basedir}&lt;/directory>
        &lt;includes>
          &lt;include>plugin.xml&lt;/include>
          &lt;include>plugin.properties&lt;/include>
        &lt;/includes>
        &lt;targetPath>/&lt;/targetPath>
      &lt;/resource>
    &lt;/resources>
    &lt;plugins>
      &lt;plugin>
        &lt;groupId>org.apache.maven.plugins&lt;/groupId>
        &lt;artifactId>maven-eclipse-plugin&lt;/artifactId>
        &lt;configuration>
          &lt;pde>true&lt;/pde>
        &lt;/configuration>
      &lt;/plugin>
      &lt;plugin>
        &lt;groupId>org.apache.felix.plugins&lt;/groupId>
        &lt;artifactId>maven-osgi-plugin&lt;/artifactId>
        &lt;version>0.8.0-SNAPSHOT&lt;/version>
        &lt;executions>
          &lt;execution>
            &lt;goals>
              &lt;goal>osgi-bundle&lt;/goal>
            &lt;/goals>
          &lt;/execution>
        &lt;/executions>
      &lt;/plugin>
    &lt;/plugins>
  &lt;/build>
  &lt;pluginRepositories>
    &lt;pluginRepository>
      &lt;id>apache.org&lt;/id>
      &lt;name>Apache Snapshot Repository&lt;/name>
      &lt;url>http://people.apache.org/repo/m2-snapshot-repository&lt;/url>
      &lt;releases>
        &lt;enabled>false&lt;/enabled>
      &lt;/releases>
    &lt;/pluginRepository>
  &lt;/pluginRepositories>
</pre></td></tr></table>

<h1>Reading Eclipse Plugins / OSGi bundles for Maven</h1>

<p>Lastest version of <a href="http://maven.apache.org/plugins/maven-eclipse-plugin/overview.html">Maven Eclipse Plugin</a> has a <a href="https://svn.apache.org/repos/asf/maven/plugins/trunk/maven-eclipse-plugin/src/main/java/org/apache/maven/plugin/eclipse/MakeArtifactsMojo.java">MakeArtifactsMojo</a> that reads Eclipse Plugins, parses the manifest to generate the poms and installs them in the repository.</p>

<h1>Building Eclipse with Maven</h1>

<p>Several barriers have been identified that prevent Eclipse platform, equinox, RCP from building using Maven. For a discussion, see <a class="confluence-link" href="/display/MAVEN/Barriers+to+Building+Eclipse+with+Maven" data-linked-resource-id="63746" data-linked-resource-type="page" data-linked-resource-default-alias="Barriers to Building Eclipse with Maven" data-base-url="http://docs.codehaus.org">Barriers to Building Eclipse with Maven</a>.</p>

<h1>General Discussion on Building OSGi</h1>

<p>I'm starting an area on the MAVENUSER confluence space to talk about how to build OSGi bundles (with Maven). I'd like to capture the current practices, whether using Ant or whatever, and use the space for reviewing possible design changes for Maven to accommodate these builds. That area will be found here:</p>

<p><a class="confluence-link" href="/display/MAVENUSER/Building+OSGi+Bundles" data-linked-resource-id="63778" data-linked-resource-type="page" data-linked-resource-default-alias="Building OSGi Bundles" data-base-url="http://docs.codehaus.org">Building OSGi Bundles</a></p>