![Oracle Drags Its Feet in the JavaScript Trademark Dispute](https://cdn.sanity.io/images/cgdhsj6q/production/919c3b22c24f93884c548d60cbb338e819ff2435-1024x1024.webp?w=400&fit=max&auto=format)
Security News
Oracle Drags Its Feet in the JavaScript Trademark Dispute
Oracle seeks to dismiss fraud claims in the JavaScript trademark dispute, delaying the case and avoiding questions about its right to the name.
@jayree/sfdx-plugin-manifest
Advanced tools
A Salesforce CLI plugin containing commands for creating manifest files from Salesforce orgs or git commits of sfdx projects.
A Salesforce CLI plugin containing commands for creating manifest files from Salesforce orgs or git commits of sfdx projects.
$ sfdx plugins:install @jayree/sfdx-plugin-manifest
$ sfdx jayree:[COMMAND]
running command...
$ sfdx plugins
@jayree/sfdx-plugin-manifest 2.4.7
$ sfdx help jayree:[COMMAND]
USAGE
$ sfdx jayree:COMMAND
...
sfdx jayree:manifest:cleanup
removes those tags from a manifest file that are present in a second manifest file
USAGE
$ sfdx jayree:manifest:cleanup [-x <filepath>] [-f <filepath>] [--json] [--loglevel
trace|debug|info|warn|error|fatal|TRACE|DEBUG|INFO|WARN|ERROR|FATAL]
FLAGS
-f, --file=<value> path to the second 'cleanup'
manifest file
-x, --manifest=<value> path to the manifest file
--json format output as json
--loglevel=(trace|debug|info|warn|error|fatal|TRACE|DEBUG|INFO|WARN|ERROR|FATAL) [default: warn] logging level for
this command invocation
DESCRIPTION
removes those tags from a manifest file that are present in a second manifest file
Use this command to remove components or metadata types from a manifes file.
If the 'cleanup' manifest file (--file) doesn't exist, a template file is created, which can then be modified.
EXAMPLES
$ sfdx jayree:manifest:cleanup --manifest=package.xml --file=packageignore.xml
See code: src/commands/jayree/manifest/cleanup.ts
sfdx jayree:manifest:generate
generate a complete manifest file form the specified org
USAGE
$ sfdx jayree:manifest:generate [-q <array>] [-c] [-w] [--includeflowversions] [-f <string>] [-x | -a] [-u <string>]
[--apiversion <string>] [--json] [--loglevel trace|debug|info|warn|error|fatal|TRACE|DEBUG|INFO|WARN|ERROR|FATAL]
FLAGS
-a, --excludeall exclude all packages from output
-c, --matchcase enable 'match case' for the
quickfilter
-f, --file=<value> write to 'file' instead of stdout
-q, --quickfilter=<value> csv separated list of metadata type,
member or file names to filter on
-u, --targetusername=<value> username or alias for the target
org; overrides default target org
-w, --matchwholeword enable 'match whole word' for the
quickfilter
-x, --excludemanaged exclude managed packages from output
--apiversion=<value> override the api version used for
api requests made by this command
--includeflowversions include flow versions as with api
version 43.0
--json format output as json
--loglevel=(trace|debug|info|warn|error|fatal|TRACE|DEBUG|INFO|WARN|ERROR|FATAL) [default: warn] logging level for
this command invocation
DESCRIPTION
generate a complete manifest file form the specified org
Use this command to generate a manifest file based on an existing org.
EXAMPLES
$ sfdx jayree:manifest:generate --targetusername myOrg@example.com
<?xml version='1.0' encoding='UTF-8'?>
<Package xmlns='http://soap.sforce.com/2006/04/metadata'>...</Package>
See code: src/commands/jayree/manifest/generate.ts
sfdx jayree:manifest:git:diff
create a manifest and destructiveChanges manifest using 'git diff' data
USAGE
$ sfdx jayree:manifest:git:diff [-p <array>] [-o <string>] [-d] [--json] [--loglevel
trace|debug|info|warn|error|fatal|TRACE|DEBUG|INFO|WARN|ERROR|FATAL]
ARGUMENTS
REF1 base commit or branch
REF2 commit or branch to compare to the base commit
FLAGS
-d, --destructivechangesonly create a destructiveChanges manifest
only (package.xml will be empty)
-o, --outputdir=<value> directory to save the created
manifest files
-p, --sourcepath=<value> comma-separated list of source file
paths to limit the diff
--json format output as json
--loglevel=(trace|debug|info|warn|error|fatal|TRACE|DEBUG|INFO|WARN|ERROR|FATAL) [default: warn] logging level for
this command invocation
DESCRIPTION
create a manifest and destructiveChanges manifest using 'git diff' data
Use this command to create a manifest and destructiveChanges manifest file based on the difference (git diff) of two
git refs.
You can use all ways to spell <commit> which are valid for 'git diff'.
(See https://git-scm.com/docs/git-diff)
EXAMPLES
$ sfdx jayree:manifest:git:diff <commit> <commit>
$ sfdx jayree:manifest:git:diff <commit>..<commit>
uses the changes between two arbitrary <commit>
$ sfdx jayree:manifest:git:diff <commit>...<commit>
uses the changes on the branch containing and up to the second <commit>, starting at a common ancestor of both <commit>.
$ sfdx jayree:manifest:git:diff branchA..branchB
uses the diff of what is unique in branchB (REF2) and unique in branchA (REF1)
$ sfdx jayree:manifest:git:diff branchA...branchB
uses the diff of what is unique in branchB (REF2)
See code: src/commands/jayree/manifest/git/diff.ts
FAQs
A Salesforce CLI plugin containing commands for creating manifest files from Salesforce orgs or git commits of sfdx projects.
The npm package @jayree/sfdx-plugin-manifest receives a total of 738 weekly downloads. As such, @jayree/sfdx-plugin-manifest popularity was classified as not popular.
We found that @jayree/sfdx-plugin-manifest demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 0 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Oracle seeks to dismiss fraud claims in the JavaScript trademark dispute, delaying the case and avoiding questions about its right to the name.
Security News
The Linux Foundation is warning open source developers that compliance with global sanctions is mandatory, highlighting legal risks and restrictions on contributions.
Security News
Maven Central now validates Sigstore signatures, making it easier for developers to verify the provenance of Java packages.