vb-manifest

Creates build manifests for the visual application’s build assets. The assets can be non-optimized (in the build/processed directory) or optimized (in the build/optimized directory).

Note: This task is a multitask so it requires an existing Grunt configuration to run. You can create your own in your Gruntfile.js or use the vb-manifest-configuration subtask to generate one.

For visual applications, it creates two kinds of manifests:

• A manifest in each web application. This manifest contains a list of application resources, requirejs bundles mapping, and the name of the version_<hash> directory. The manifest location is build/[processed|optimized]/webApps/<applicationName>/build-info.json.

• A manifest for the visual application itself, which contains the URL of the sources Git repository. The manifest location is build/[processed|optimized]/build-info.json.

For Oracle Cloud Application extensions, it creates one manifest in build/[processed|optimized]/manifest.json.

The following table describes the subtasks, hooks, and inputs and outputs of the vb-manifest task:

Detail	Description
subtasks	n/a
multitask	config generator task: vb-manifest-configuration
hooks	n/a
input	build/[processed|optimized]/*
output	build/[processed|optimized]/*

The following table describes the options for the vb-manifest task:

Name	Mandatory	Default Value	Description
target	no	build	Name of build directory.
vx-version	no	n/a	Overwrites 'version' key in an extension's manifest with the given value. This option is only used for application extensions.
git-repository-url	no	The Git repository URL read from ${gitSources}/.git/config .	URL of the application's source repository. The value is written into the generated build manifest of the visual application ( build/optimized/build-info.json ) under the git-repository-url key.