A wizard appears that lets you specify the plug-in name, a description, the Apama package name, the Java source folder and the Java package. See also Adding an EPL Plug-in written in Java.

Software AG Designer automatically adds an entry for the EPL plug-in to the jmon-jar.xml deployment descriptor file and regenerates the JAR file to include the new plug-in.

If you want to build your JAR files manually, right-click your project and select Apama > Build JAR Files. This is useful if you unselected the Build jar files automatically option in the apama_java.xml file, which is in the config directory of your project. One reason you might not want to build the JAR files automatically is that the build takes too long. When Build jar files automatically is selected, Software AG Designer builds the JAR files every time you modify the EPL plug-in.

If you want to build your project's files outside Software AG Designer and Eclipse, right-click your project and select Apama > Generate Ant Buildfiles. Software AG Designer generates an Ant build file (with the name build-project_name.xml), which you can use only to build your project's plug-in JAR files outside of the Eclipse environment. Note that this is unrelated to the Software AG Designer feature for exporting an Ant build file that you can use for deployment. See also Defining custom launch configurations.

You can manage the content of the plug-in JAR file and jmon-jar.xml file by using the editor in Software AG Designer to update the apama_java.xml file, which is located in the project's config folder. You can use this editor to do the following: