Plugins new style

Ruben de Laat edited this page Feb 2, 2016 · 5 revisions
Clone this wiki locally

For the BIMserver 1.5 release, plugins have changed quite a bit.

For starters they depend on maven now. In the long term the plan is to also support non-maven plugins, but for now it's a requirement. To make the transition for older plugins easier, and to help developers of new plugins, this document describes how it works.

BIMserver specific terminology:

  • Plugin: A plugin (implementing org.bimserver.plugins.Plugin)
  • PluginBundle: A collections of 1 or more plugins, for example the org.opensourcebim.ifcplugins bundle has 18 plugins, but a lot of bundles only have 1 (for example org.opensourcebim.ifcopenshellplugin)

Create a maven project

Most Java IDEs should support this. There should be one pom.xml file per plugin bundle. In the next section all required parts in the pom.xml will be described, most of them are enforced by maven(relase plugin), ans some by BIMserver pluginmanagement.



For most plugins for bimserver this is org.opensourcebim, but this can be anything of course, make sure to use lowercase, which is the convention


This should describe your plugin bundle, also make sure it is lowercase


Make sure your version on SCM always ends in -SNAPSHOT and releases always omit -SNAPSHOT


This is just to make sure build results are repeatable on different platforms

<description>BIMserver plugin that uses IfcOpenShell to generate geometry from IFC files</description>

A description for the whole bundle.


This is used by the maven release plugin to push/pull to the SCM.

        <name>OpenSource BIM</name>

Some information about the organization, of course you should fill in the details about your organization.

            <name>GNU Affero General Public License</name>
            <name>Ruben de Laat</name>