DarchetypeArtifactId=maven-archetype-quickstart -DinteractiveMode=false
![deployit maven plugin deployit maven plugin](https://tibcosoftware.github.io/tibco-streaming-maven-plugin/1.5.0/ep-maven-plugin/images/jenkins-new-project.png)
% mvn archetype:generate -DgroupId=com.pushtechnology -DartifactId=echo First let’s start with a new Maven project. You should be able to translate these to the corresponding actions for other operating systems.
![deployit maven plugin deployit maven plugin](https://ammblog.azurewebsites.net/wp-content/uploads/2018/06/d45609d5-aa94-4610-84a3-a73d7fde83a0-800x413.png)
The following shows the actions taken from my Linux command line, with the DIFFUSION_HOME environment variable set to the location of a Diffusion 4.5.4 installation.
#DEPLOYIT MAVEN PLUGIN CODE#
If you selected the examples when you installed Diffusion, the EchoServer source code can be found in the Diffusion product directory below examples/publishers. Let me take you through the steps of packaging the EchoServer sample publisher as a DAR. Simply change the packaging type in your pom file, and Maven will orchestrate the compilation, testing, and packaging of your DAR, and optionally publish it to a Maven repository for distribution to other projects. Because mvndar inherits Maven’s “configuration by convention” approach, you need do very little to use it. The mvndar plugin takes care of the packaging for you, so you no longer need custom scripts. Previously the best way to automate the process of packing application code and configuration into this structure was to use an Ant script, or perhaps the Maven assembly plugin. Please refer to the Diffusion documentation for details. The server expects the contents of a DAR file to be arranged in a particular structure. They have a similar purpose to Java EE EAR or WAR files, and can be dynamically deployed to and undeployed from a running Diffusion server. DARs are jar format files that contain compiled code, libraries, and configuration.
#DEPLOYIT MAVEN PLUGIN ARCHIVE#
The preferred way to deploy publishers is to package them into a Diffusion Archive ( DAR) file. This is simple, but doesn’t allow a publisher to be changed or reconfigured without restarting the server.
![deployit maven plugin deployit maven plugin](https://2.bp.blogspot.com/-2LCWVAKEZpY/XD3NmmVHUVI/AAAAAAAAdPM/YChf02gC07spw7PP0AoUynAPof7zQItgACLcBGAs/s1600/mule-maven-plugin-1.png)
Publishers can be configured statically in the server’s etc/Publishers.xml file. Since it’s good practice to package logically separate parts of an application as separate publisher implementations, more complex applications may have several publishers. Most Diffusion applications have at least one publisher. A publisher can send messages to topics, and hence to clients, and process messages received from clients. Publishers are server-side components that run in a Diffusion server and act as central switchboards for your application. It’s open source, available from GitHub, and you can use it today. Automatic addition of a Diffusion-Version header to the DAR manifest.
![deployit maven plugin deployit maven plugin](https://i.ytimg.com/vi/-DvIJE1r72U/hqdefault.jpg)