Skip to content

Set up your plugin development project

When you develop your plugin, you will extend classes from the OmegaT project, or call methods. To be able to compile your project, you need the OmegaT dependencies. You can either stub them, copy them individually, or just include the entire OmegaT project .jar file in your project. But you have to make sure these files are not part of the .jar file that you produce.

Gradle example

An example of how to configure the plugin project in a Gradle project. You can use skeleton project as a project template forked from


plugin {
    id 'org.omegat.gradle' version '1.5.11'
omegat {
} Filter Name
plugin.category=filter name here.
plugin.description=I describe my plugin here. This plugin does amazing things
plugin.license=GNU General Public License version 3

maven example

An example of how to include OmegaT code to your project in a Maven project, without adding it to the compiled .jar file:


The above example goes in your pom.xml file under <dependencies>. The scope is the magic here. But if you want to run OmegaT with your plugin under development, then you'd have to temporary remove <scope>provided</scope>.

To produce a .jar file, you can use the maven-jar-plugin as seen below. If you used stubs or copied OmegaT .java files to your project, you can exclude them from the .jar file using the <excludes> section.

                        <!-- gives Implementation-Title: $
                                   Implementation-Version: $project.version
                                  [Implementation-Vendor: $]
                        <Plugin-Description>I describe my plugin here. This plugin does amazing things</Plugin-Description>
                        <Plugin-Author>Your name here.</Plugin-Author>
                        <Plugin-License>SPDX identifier such as GPL-3</Plugin-License>