In this example run-java module is loaded as a plugin(considered as an include).Īs easyant proceeds with execution, all targets are imported in current project.īuild plugins are there to actually define each block of the build system. You can load several plugins using the plugin tag. But sometimes we need something more (Source code management feature / code coverage etc.). You can also have property definition, as you would have in an Ant script 'ea:build' tag is the main instruction, arguments references a build type, which tells which build module should be imported (considered as an import), see below. If you need more, you can use a module.ant file. The idea is to have a very limited options to customize the build in the Ivy file: settings properties, specify build modules (buildtype / plugins). In the examples, there is no such file, but this would let the user customize the build with an Ant script if necessary.ĮasyAnt intructions in module.ivy files looks like this Then it uses the loadmodule task provided by easyant, which basically parses an Ivy file (module.ivy similar to pom.xml for maven) and looks for easyant instructions.įinally easyant tries to import an optional file called module.ant in the user directory (the module to build). This can be configured in a configuration file. Loading the ivy instance used by easyant internal (used to retrieve buildtypes / plugins).

If you don't know EasyAnt at all, give a glance at its features, the FAQ and the tutorials before digging into this reference documentation.

Apache ant doc