Chapter 11. Deploying and Managing Projects
Once you have created a project with your process definition and relevant resources, you need to build it and deploy it to the process engine. Once deployed, you can create process instances based on the deployed resources.
11.1. Deploying a Project
To deploy your project from Business Central, do the following:
- Open the Project Editor in your project (navigate to your project using Project Explorer and click Open Project Editor).
- You can define the Kie Base and Kie Session properties. If not, the default kbase and ksession will be used.
- On the title bar, click Build → Build & Deploy.
From the 6.1 version of Red Hat JBoss BPM Suite, deployment units are stored inside the database instead of the GIT repository. To override this behavior, set the org.kie.git.deployments.enabled property to true.
11.1.1. Duplicate GAV Detection
Every time you perform any of the operations listed below, all Maven repositories are checked for duplicate GroupId, ArtifactId, and Version. If a duplicate exists, the performed operation is cancelled.
The duplicate GAV detection is executed every time you:
- Create a new managed repository.
- Save a project definition in the Project Editor.
- Add new modules to a managed multi-module repository.
-
Save the
pom.xmlfile. - Install, build, or deploy a project.
The following Maven repositories are checked for duplicates:
-
Repositories specified in the
<repositories>and<distributionManagement>elements of thepom.xmlfile. -
Repositories specified in the Maven’s
settings.xmlconfiguration file.
Users with the admin role can modify the list of affected repositories. To do so, open your project in the Project Editor and click Project Settings: Project General Settings → Validation.
Figure 11.1. List of Repositories to Be Checked
Figure 11.2. Duplicate GAV Detected
To disable this feature, set the org.guvnor.project.gav.check.disabled system property to true.
Where did the comment section go?
Red Hat's documentation publication system recently went through an upgrade to enable speedier, more mobile-friendly content. We decided to re-evaluate our commenting platform to ensure that it meets your expectations and serves as an optimal feedback mechanism. During this redesign, we invite your input on providing feedback on Red Hat documentation via the discussion platform.