Security News
tea.xyz Spam Plagues npm and RubyGems Package Registries
Tea.xyz, a crypto project aimed at rewarding open source contributions, is once again facing backlash due to an influx of spam packages flooding public package registries.
mvn-deploy-file
Advanced tools
Readme
A Node.js wrapper for mvn deploy:deploy-file for deploying files to a Nexus repository using information in a config file or package.json.
npm i mvn-deploy-file -g
# With a separate config file
mvn-deploy-file snapshot *.rpm --config=config.json
# With config in package.json
mvn-deploy-file snapshot *.rpm
# With options
mvn-deploy-file snapshot *.rpm \
--groupId="com.myorg.mygroup" \
--url="http://nexus.myorg.com/content" \
--repositoryId="snapshots"
var mvnDeployFile = require('mvn-deploy-file')
var minimist = require('minimist')
var options = minimist(process.argv.slice(2))
var args = options._
delete options._
mvnDeployFile(args, options, function onMvnDeployFile (err, url) {
if (err) {
throw err
}
console.log('Uploaded: ', url)
})
{
"snapshot": {
"groupId": "com.myorg.mygroup",
"url": "http://nexus.myorg.com/content/snapshots",
"repositoryId": "snapshots"
},
"release": {
"groupId": "com.myorg.mygroup",
"url": "http://nexus.myorg.com/content/snapshots",
"repositoryId": "snapshots"
}
}
If you are using config.json or command-line options:
{
"name": "mvn-deploy-file",
"version": "1.0.0",
}
If you are storing options in package.json
{
"name": "mvn-deploy-file",
"version": "1.0.0",
"mvn-deploy-file": {
"snapshot": {
"groupId": "com.myorg.mygroup",
"url": "http://nexus.myorg.com/content/snapshots",
"repositoryId": "snapshots"
},
"release": {
"groupId": "com.myorg.mygroup",
"url": "http://nexus.myorg.com/content/snapshots",
"repositoryId": "snapshots"
}
}
}
All the examples above result in this command being executed:
mvn -e deploy:deploy-file \
-Durl="http://nexus.myorg.com/content/snapshots" \
-DrepositoryId="snapshots" \
-DgroupId="com.myorg.mygroup" \
-DartifactId="mvn-deploy-file" \
-Dversion="1.0.0-SNAPSHOT" \
-Dpackaging=rpm \
-Dfile="something.rpm"
mvn-deploy-file [config-key [glob-pattern]]
-SNAPSHOT
will be appended to the versionAll command line options accepted by mvn -e deploy:deploy-file map to equivalent
options for this tool except -D
is replaced with --
For example -Dpackaging
=== --packaging
There is also the additional option, unique to this tool, of --config
for
specifying a configuration separate from package.json
For the --file
option, a glob pattern can be used.
The root object has config-keys that map to the first command line argument.
Each of the options under a config-key are the same as command line options
except that config
is not valid.
The name
and version
in a package.json map to artifactId
and version
respectively.
Each of the following overwrites the options beneath it:
The following values are pulled from a normal package.json:
pkg.name ==> -DartifactId pkg.version ==> -Dversion
In both the config.json and mvn-deploy-file section of package.json options are pulled directly based on the first command line argument.
If 'snapshot' is found anywhere in the first command line argument, the version has "-SNAPSHOT" appended to it, otherwise these config keys may be anything and as many as you wish.
FAQs
A wrapper for mvn deploy:deploy-file for quickly pushing files to a Nexus repository.
The npm package mvn-deploy-file receives a total of 2 weekly downloads. As such, mvn-deploy-file popularity was classified as not popular.
We found that mvn-deploy-file demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 2 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
Tea.xyz, a crypto project aimed at rewarding open source contributions, is once again facing backlash due to an influx of spam packages flooding public package registries.
Security News
As cyber threats become more autonomous, AI-powered defenses are crucial for businesses to stay ahead of attackers who can exploit software vulnerabilities at scale.
Security News
UnitedHealth Group disclosed that the ransomware attack on Change Healthcare compromised protected health information for millions in the U.S., with estimated costs to the company expected to reach $1 billion.