c2c.recipe.jarfile
A buildout recipe to create or update jar archive file.
Requirements
Requires zc.buildout and the ‘jar’ command.
Usage
Create a buildout.cfg file which contains the following:
[buildout] parts = updatewar [updatewar] recipe = c2c.recipe.jarfile basedir = foo/bar/ input = base.war *.png baz/config.yaml WEB-INF/ output = /path/to/tomcat/webapps/foobar.war mode = update
Where:
‘basedir’ is the directory where the jar will be created.
‘input’ items are the files to be included in the final jar, they must be relative to ‘basedir’.
‘output’ is the jar destination (eg. a tomcat webapps directory)
‘mode’ [create|update] create a new archive using all the files in ‘input’ or create an updated version of the first item of ‘input’ using the rest of the files
- TODO:
jar cmd in config file
Metadata
Release files for c2c.recipe.jarfile 0.4.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| c2c.recipe.jarfile-0.4.3.tar.gz | 2.9 kB | Without provenance | Details for c2c.recipe.jarfile-0.4.3.tar.gz |
Release files / c2c.recipe.jarfile-0.4.3.tar.gz
| Download URL | c2c.recipe.jarfile-0.4.3.tar.gz |
|---|---|
| Size | 2.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8e7ded2f7940ae33669f06ea10986ac7a29e13814bbc8188d4f6533bb3ec36ad
|
|
BLAKE2b-256 checksum How to use checksums |
d75cdea8b44b681b7647ec94d232c8db60873ff60a2b650dad202630c836b063
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for c2c.recipe.jarfile 0.4.3
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.