This part of the docmentation will guide you through the steps that are needed in order to work with the Maven Plugin.
A Maven build is driven by Project Object Model file (POM - pom.xml). This file controls what needs to be build and how to build it. The following section needs to be included in the build section of the pom file in order to allow maven to find and use the Plugins
</build> </plugins> <plugin> <groupId>com.aurea.maven.plugins</groupId> <artifactId>sonicesb-maven-plugin</artifactId> <version>PLUGIN VERSION NUMBER (2013-RC4)</version> <extensions>true</extensions> <configuration> <containerMap> <esbContainerSettings> <DefaultContainerSetting> <name>ESBContainer</name> </DefaultContainerSetting> </esbContainerSettings> <mfContainerSettings> <DefaultContainerSetting> <name>@MFESBContainer@</name> </DefaultContainerSetting> </mfContainerSettings> </containerMap> </configuration> </plugin> </plugins> </build>
The package identifier is usually defined with the artifact and group id's
<groupId></groupId> <artifactId></artifactId> <version>2013-SNAPSHOT</version> <name>Sonic ESB Process</name> <description></description> <packaging>esb</packaging>
The maven plugin for the ESB knows 5 different packaging types. Depending on the packaging types the maven plugin will build the following artifacts:
package id | Description |
esbstyp | This instructs the maven plugin to build the ESB Service Type that is present in the project |
esb | This is the package indicator to build ESB Projects |
sdm | Package indicator to create SDM Packages |
connect | Builds a Sonic Connect project |
topology | Builds a Topology generation project |