Savant Build Tool: Plugins

Brian Pontarelli
  • By Brian Pontarelli
  • Technology
  • November 18, 2014

Savant Plugins

Savant is a bit different than other build tools. Savant doesn’t allow plugins to define build targets. This was a major design decision that we made based on our use of various build tools over the past 10 years.

Here’s the reason we decided not to allow plugins to define build targets. Let’s say that we are using the Java, Groovy and JRuby plugins and that our project has source code in all three languages. Let’s also assume we have tests written in all three languages. The Java plugin defines two build targets: compile and test. These targets compile the Java source code in the directory src/main/java and src/test/java and then execute the tests.

Now, let’s assume that our Groovy and JRuby plugins also define these exact same targets. However, our project’s Groovy classes use our Java classes and our JRuby classes use our Groovy classes. How do we ensure that our plugins are executed in the correct order?

This is complicated and requires the build tool to have a concept of “synthetic targets”. These are targets that don’t actually do anything, they just delegate to other targets. Each plugin now defines a different target called _compile which is a “hidden” target. By default, the compile synthetic target calls all _compile targets in an arbitrary order. If we want to change the order, we need to change it by hand in our build file like this:

This is not very obvious and as the build file maintainer, you have to understand how these plugins work and what hidden targets they have. You might also have to manage complex dependencies between plugins and plugin targets.

Now, let’s assume that our project needs to setup a database before the Java tests are run and reset the database before the Groovy and JRuby tests are run. We often have to inject these steps into pre and post hooks for plugin targets like this:

This is a simple example, but it illustrates the challenges build file writers face when plugins define build targets.

After using tools such as Maven and Gradle, we felt that this model was extremely complex and provided only a single benefit: standard target names. We didn’t feel that this benefit was worth the complexity.

Therefore, we took a different approach in Savant. Savant plugins provide isolated functionality through public methods on an object. Build targets are defined in the build file and call the plugin methods.

As an example, the Savant Java plugin provides the ability to compile Java source files. The Savant Java TestNG plugin provides the ability to execute TestNG tests. The Java TestNG plugin is completely isolated from the Java plugin and it will correctly fail if your build file hasn’t compiled the source code yet.

Here’s a simple build file that uses the Java and Java TestNG plugins:

That’s it! The build file defines the targets and the dependencies between them and the plugins handle all the heavy lifting of compiling the Java source files and then executing the tests. The only thing you need to ensure is that all your build files use standard names.

In case you were wondering about the example above, Savant might handle it like this:

This is just an example because Savant doesn’t yet have a JRuby plugin, but it illustrates the power and simplicity of Savant since it leaves the job of defining build targets and order of execution up to the project build file.

You can learn more about the Savant plugins, including how to write your own plugin here:

http://github.com/inversoft/savant-core/wiki

Stay tuned for our next Savant blog on how Savant allows you to quickly release your project and publish your project’s artifacts.

Tags:
Savant