This section explains how to incorporate your COBOL JVM and COBOL JVM unit testing projects into a Maven lifecycle.
These projects utilize the official Maven plugin for Eclipse, M2Eclipse, which provides tight integration with the Maven lifecycle from within the IDE: projects assume a Maven nature, which partially automates the POM file creation with regards to dependencies, as these can be taken from your current project settings.
For new Maven projects, Enterprise Developer provides two archetypes - microfocus-coboljvm-archetype for COBOL JVM projects, and microfocus-coboljvm-mfunit-archetype for COBOL JVM unit test projects. These projects can still be built as you would any other conventional JVM COBOL or JVM COBOL unit test project, but they are now also capable of being built for Maven: using the M2Eclipse plugin, you can build and package your COBOL output as Maven artifacts, and manage your Maven repositories.
These archetypes contain a number of Micro Focus-specific goals that can be incorporated into the lifecycle; seeMicro Focus-related Maven goals.
You can also make your existing COBOL JVM and COBOL JVM unit testing projects Maven-based by using the Convert to Maven Project option.
Maven-based projects contain a pom.xml file, which is central to Maven. On making a Micro Focus project Maven-based, some Micro Focus-specific goals are added to the POM in order to incorporate these COBOL projects into a Maven life-cycle when they are built. For more information on the Maven life-cycle, refer to the Maven Getting Started Guide.