#Deployit maven plugin manual
#Deployit maven plugin full

Metadata services (MDS) with schema definitions, service contracts and mappingsĢ. Each category should have no internal dependency.ġ. Logically, 2 and 3 may have elements of which deployment depend on 1 and also 3 may depend on 2. Service implementations (business and proxy services) Service contract elements (WSDL, schema definitions)ģ. Common definitions, which are shared among multiple servicesĢ. SB resources are separated by their “nature” into project categories:ġ. The largest set of artifacts consists of Oracle Service Bus resources and SOA services, including metadata service (MDS) and service component architecture (SCA). Individual artifact types may be refined easily without implementing a new plugin 2 The Case XL Deploy uses the following default orders:Įach plugin, either distribution or community, is defaulting each of its types’ create, modify and destroy order property into one of these values. The core process defines default orders, related to the base types.

#Deployit maven plugin manual

This diagram from the Customization Manual shows this cooperation (puzzle pieces represent plugin jobs):Įach plugin defines its own artifact types derived from their base UDM type in hierarchy. One of the main challenges was to determine the proper order of the steps within the deployment plan considering the dependencies between the several artifacts.ĭeployment with XL Deploy is a joined activity between its core process and its plugins. The selected deployment tool is XL Deploy from XebiaLabs. The deploy goal of the plugin is mapped to the deploy phase of the Maven build.Īlso notice that, as discussed, we do not need staging functionality in a simple deployment of -SNAPSHOT artifacts to Nexus, so that is fully disabled via the element.īy default, the deploy goal includes the staging workflow, which is recommended for release builds.The last couple of months I have been assigned to a project dedicated to deployment automation including several levels and types of technologies: database, middleware, services and portals. So, the first step in using another deployment plugin in the deploy phase is to disable the existing, default mapping: However, unlike other components that may actually change throughout the lifecycle of a project, the Maven Repository Manager is highly unlikely to change, so that flexibility is not required. The only reason to use the maven-deploy-plugin is to keep open the option of using an alternative to Nexus in the future – for example, an Artifactory repository.

#Deployit maven plugin full

Because of that fact, Sonatype built a Nexus specific plugin – the nexus-staging-maven-plugin – that is actually designed to take full advantage of the more advanced functionality that Nexus has to offer – functionality such as staging.Īlthough for a simple deployment process we do not require staging functionality, we will go forward with this custom Nexus plugin since it was built with the clear purpose to talk to Nexus well. The maven-deploy-plugin is a viable option to handle the task of deploying to artifacts of a project to Nexus, but it was not built to take full advantage of what Nexus has to offer.

By default, Maven handles the deployment mechanism via the maven-deploy-plugin – this mapped to the deployment phase of the default Maven lifecycle: