Filters

CLEAR ALL

Search Results ()

Filter Icon

Search Results ()

    All Plugins (172)

    Filter Icon

    Quick Info

    Product icon
    Product
    DevOps Deploy (HCL Launch)
    Plugin type icon
    Type
    plugin
    Compatibility icon
    Compatibility
    This plug-in requires version 6.0.1 or later of HCL UrbanCode Launch.
    created by icon
    Created by
    HCL Software
    Website icon
    Website
    Published Date
    February 22nd, 2024
    Last Updated
    June 6th, 2024

    Description

    Maven Resolve is a software project management and comprehension tool. Based on the concept of a project object model (POM), Maven Resolve can manage a project’s build, reporting, and documentation from a central piece of information. The Maven Resolve plug-in supports resolving artifacts from a Maven repository.

    Quick Info

    Product icon
    Product
    DevOps Deploy (HCL Launch)
    Plugin type icon
    Type
    plugin
    Compatibility icon
    Compatibility
    This plug-in requires version 6.0.1 or later of HCL UrbanCode Launch.
    created by icon
    Created by
    HCL Software
    Website icon
    Website
    Published Date
    February 22nd, 2024
    Last Updated
    June 6th, 2024

    launch-maven-11.1167755.zip

    Uploaded: 02-May-2024 08:37

    Release Notes

      Log4j and Jettison dependency updated.

    launch-maven-10.1126874.zip

    Uploaded: 23-Dec-2021 06:21

    Release Notes

      Log4j issue addressed.

    Maven-9.982528.zip

    Uploaded: 22-Feb-2024 11:31

    Release Notes

      Fixes APAR PI98904 Support resolving Maven snapshot versions using hidden property. Function requires Maven Source Config plug-in version 13 or later.

    Overview

    The Maven Resolve plug-in includes a step that resolves artifacts from a Maven repository:

      Maven Resolve

    You can use the Maven Resolve plug-in if you already have a Maven repository in use as the definitive source for artifacts. In this scenario, your build automation tool stores new builds in the Maven repository and creates a corresponding empty component version in HCL Devops Deploy, where the name of the component version matches the Maven identifier. Then, instead of using the Download Artifacts step, you use the Maven Resolve plug-in to retrieve the artifacts from the Maven repository and deploy them on the agent computer.

    To add the Maven Resolve plug-in steps to processes, click Repositories > Artifact > Maven in the step palette of the process editor.

    To use a Maven repository with the Codestation repository in HCL DevOps Deploy, see the Maven source configuration plug-in.

    Compatibility

    This plug-in requires version 6.0.1 or later of HCL Launch/DevOps Deploy.

    Installation

    Installing plugins in HCL Launch for installing and removing plugins.

    History

    The following table describes the changes made in each plugin version.

    Plugin history details
    Version Description
    10 Log4j issue addressed.
    9 Fixes APAR PI98904 Support resolving Maven snapshot versions using hidden property. Function requires Maven Source Config plug-in version 13 or later.
    8 Support property file encryption.
    7 Update Maven resolve step to split artifacts properly.
    6 Fixes APAR PI35342 – compatibility defect with HCL Launch version 6.1.0.4 and later.
    5 Modified the optional step properties default to use optional server properties. This prevents the step from failing because if these server properties are undefined.
    4 Updated plugin to allow user to configure a http proxy when resolving artifacts.
    3 Updated the input format for artifacts.
    2 Updated plugin defaults to point to component source configuration, making pulling from maven easier to configure.
    1 Install this plugin to access to the steps when designing a component process.

    Steps

    The resolve artifacts from Maven Resolve are as follows:

    Steps for the Maven Resolve
    Name Type Description Required
    Artifacts String Line-separated list of artifacts to download. Specify using the form groupId/artifactId/version/filename. Yes
    HTTP Proxy Hostname String (Optional) HTTP proxy host. No
    HTTP Proxy Password Password (Optional) HTTP proxy password. No
    HTTP Proxy Port String (Optional) HTTP proxy port number. Must be specified if HTTP proxy host is specified. No
    HTTP Proxy Username String (Optional) HTTP proxy user name. No
    Repository Password Password The password to authenticate with Maven. No
    Repository URL String The base URL of the Maven repository. Yes
    Repository Username String The user name to authenticate with Maven. No
    Verify Hash Boolean Verify hashes after the file is downloaded. No

    Usage

    The format that is required by the Artifacts field in the Maven Resolve step is:

    groupId/artifactId/version/filename.

    The default value of the Artifacts field is:

    ${p:component/MavenComponentProperties/groupId}/${p:component/MavenComponentProperties/artifactId}/${p:version.name}/${p:component/MavenComponentProperties/artifactId}-${p:version.name}.${p:component/MavenComponentProperties/extension}.

    You must configure the component properties that are used in the Artifacts field before you run the Maven Resolve step. To learn more about component properties, see Component properties in the product help.

    The default value of the Artifacts field uses the following combination of properties for the file name: ${p:component/MavenComponentProperties/artifactId}-${p:version.name}. ${p:component/MavenComponentProperties/extension}.

    Configure the properties so that the file name matches the file name in the Maven repository.