v24.1.0

Story
[VDS-532] - Validate Vault Client
[VDS-958]- Remove Duplicate Logging
Bug
[VDS-959]- Exceeding Job Status Polling API Limit

v23.1.0

    Release Notes - Vault Developer Support - Version Maven Plugin v23.1.0

Story

• [VDS-30] - Add support for plugin settings file
• [VDS-69] - VAPIL Settings File Support
• [VDS-247] - Upgrade Dependencies

v22.3.0

    Release Notes - Vault Developer Support - Version Maven Plugin v22.3.0

Story

• [VDS-63] - Remove Package ID parameter
• [VDS-64] - Update Vapil version

Bug

• [VDS-55] - Job Polling exception occuring during VPK deployment

v22.2.1

    Release Notes - Vault Developer Support - Version Maven Plugin v22.2.1

Story

• [VDS-29] - Replace System.out.println with Logger

v22.2.0

    Release Notes - Vault Developer Support - Version Maven Plugin v22.2.0

Story

• [VDS-26] - Use VAPIL for all Vault API calls
• [VDS-27] - Build and Deploy jar file
• [VDS-28] - Include Shaded jar in Deployment

v1.0.2

Release v1.0.2. Added support to default the username to "Vault Java SDK Maven Plugin" when the username parameter is empty.

• The username is used to populate the required "author" value in the vaultpackage.xml.

v1.0.1

Release v1.0.1. Added support for new input parameters to use custom packages and already imported packages:

• <package> - optional, define a custom VPK to deploy. The VPK must exist in '{{PROJECT_DIRECTORY_PATH}}/deployment/packages'
• <packageId> - optional, deploy a specific imported package ID. To be used in conjunction with the vaultjavasdk:import goal. The ID can also be retrieved from the vault UI.

v1.0.0

Initial release of the vaultjavasdk-maven-plugin. This release contains goals that:

• vaultjavasdk:clean - removes all files in the “deployment” folder in the maven project. This folder contains VPK files and vaultpackage.xml file created by this plugin.

• vaultjavasdk:package - generates a VPK file in the "deployment/packages" directory.

  • VPK file name format: code_package_{mm-dd-yyyy}_{num}.vpk
  • If the directory does not exist, it will be created.
  • If a VPK already exists, increment {mm-dd-yyyy} and/or {num}
  • Source files under the “javasdk/src/main/java/com/veeva/vault/custom” folder in the project are zipped into a VPK file.

• vaultjavasdk:deploy - validates, imports, and deploys the last modified VPK in the "deployment/packages" directory it to a vault.

• vaultjavasdk:validate - validates the last modified VPK in the "deployment/packages" directory against the Validation Endpoint.

• vaultjavasdk:import - validates and imports the last modified VPK in the "deployment/packages" directory to a vault. This is optional and is intended for verifying package in Vault Admin UI before deploying via the Vault Admin UI.