Open topic with navigation

TIBCO BusinessEvents® Enterprise Edition 6.3.1

# Generating POM File Using BusinessEvents Studio Tools Utility

TIBCO BusinessEvents provides the `convertToMaven` utility that converts a BE project to a native Maven project, generating the pom.xml file in the process. This pom.xml file is saved at the BusinessEvents project root level.

You can generate the pom.xml file from the studio-tools utility in the following situations:

- To convert an existing BusinessEvents non-Maven project from 6.3.1 or older versions to a Maven project.
- To re-generate pom.xml if the existing pom.xml is accidentally deleted or corrupted.
- To generate the new structured pom.xml for 6.3.1 or older versions of BusinessEvents Maven projects that have the old structured pom.xml.

Note:

- If the pom.xml file is deleted, then the BusinessEvents Project Nature and Builder are removed and the corresponding BusinessEvents features are disabled for the project.
- The project effectively removes the BusinessEvents functionality from the project. However, to add the BusinessEvents Studio nature, see Adding Studio Nature to the Project.

Before you beginTIBCO BusinessEvents Maven plug-in is set up in your repository. See Setting Up TIBCO BusinessEvents Maven Plug-in for more details.

The following procedure explains the steps to generate pom.xml using the `convertToMaven` utility.

Procedure

1. In the command line, navigate to the studio tools `bin` folder in the TIBCO BusinessEvents installation at BE_HOME/studio/bin.

2. Run the following command:

       - studio-tools -core convertToMaven -p <studioProjDir> [-g <groupId>] [-m] [-r] [-x]

   The `convertToMaven` Utility Parameters
   Options | Description
   --- | ---
   `-p` | Absolute path to the TIBCO BusinessEvents Studio project directory to be converted, or the root directory of all Studio projects if -r is specified. The pom.xml file is generated for this project.
   `-g` | Optional. A unique group ID for the converted Maven project amongst an organization. If not specified, the default group ID `com.tibco.be` is used.
   `-m` | Optional The option allows to create a multi-module project. Specifying this tag converts all Studio projects found in the provided directory and creates a multi-module Maven project.
   `-r` | Optional. It processes all Studio projects recursively in the provided path.
   `-x` | Optional. Overwrites any existing pom.xml files.

   For example, to generate a pom.xml file for the FraudDetection example, run the following command:

       - studio-tools -core convertToMaven -p BE_HOME/examples/standard/FraudDetection/FraudDetection -g com.tibco.be

   ResultA pom.xml file is generated for the FraudDetection project at the BE_HOME/examples/standard/FraudDetection/FraudDetection location.

## Adding Studio Nature to the Project

If a pom.xml is deleted, you can re-generate it for the project. When you select a Studio project nature, you effectively add the TIBCO BusinessEvents functionalities to the project. The BusinessEvents Studio nature is added to the project by performing the following steps:

Procedure
1. Select the project and navigate to Project Properties > Project Nature.
2. To add the Studio project nature to the project, select Studio Project Nature.
3. Click Apply and Close.

Note:

- Select Maven Nature to add Maven nature to the project.
- Add the dependencies in pom.xml, if required, after you add Studio Project Nature to the project.

Did you find this helpful?

YesNo
Great!
Thanks for taking the time to give us some feedback.
Sorry about that

Why wasn't this helpful? (check all that apply)

Could not find what I was looking for
Instructions confusing or unclear
Instructions did not work

Want to tell us more?

Please select at least one option or provide details about the issue!!

Error occurred while submitting feedback.

Error2 occurred while submitting feedback.

TIBCO BusinessEvents® Enterprise Edition

Copyright © 2004-2024. Cloud Software Group, Inc. All Rights Reserved.