This release is a pre-release and may not be stable for production use.
collective.recipe.ant package
=============================
.. contents::
What is collective.recipe.ant ?
===============================
Collective.recipie.ant executes an ant build. It assumes java, and and ant
is installed on the system.
Supported options:
ant
Specify the location of the ant application. This option is optional.
If not used the application is looked up in the default path
ant-home
If ant is not located in your default ``PATH```-environment variable
you can specify the location here
ant-options
Specify the options ant should be called with. You may change the
buildfile with the ```-buildfile```option for example.
classpath
Give some extra location for including java libraries.
I.e. junit, ...
You can debug the ant output by increasing the verbosity of buildout.
Simple example
==============
>>> import os.path
In the simplest form we can download a simple package and have it
extracted in the parts directory.
>>> write(sample_buildout, 'buildout.cfg',
... """
... [buildout]
... parts = javaproject
...
... [javaproject]
... recipe = collective.recipe.ant
...
... """)
Ok, let's run the buildout:
>>> print system(buildout)
Installing javaproject.
Build failed
While:
Installing javaproject.
Error: System error: Buildfile: build.xml does not exist!
<BLANKLINE>
<BLANKLINE>
This one failed. We didn't specify any options. Let's do that.
>>> from os.path import join, dirname
>>> buildfile = join(dirname(__file__), 'testdata', 'echo.xml')
>>> write(sample_buildout, 'buildout.cfg',
... """
... [buildout]
... parts = javaproject
...
... [javaproject]
... recipe = collective.recipe.ant
... ant-options =
... echo
... -buildfile %s
...
... """ % buildfile)
Fetch the output of the ant process, when being extra verbose
>>> print system(buildout + ' -v')
Installing ...
<BLANKLINE>
echo:
[echo] Foo Bar
<BLANKLINE>
BUILD SUCCESSFUL
Total time: 0 seconds
<BLANKLINE>
javaproject: Build successful
<BLANKLINE>
Let's see if the classpath verification works
>>> write(sample_buildout, 'buildout.cfg',
... """
... [buildout]
... parts = javaproject
...
... [javaproject]
... recipe = collective.recipe.ant
... classpath = %s %s
... ant-options =
... echo
... -buildfile %s
...
... """ % (join(dirname(__file__), 'testdata'),
... tmpdir('foo'),
... buildfile))
>>> print system(buildout)
Uninstalling javaproject.
Installing javaproject.
javaproject: Build successful
<BLANKLINE>
Now we try to reference a (hopefully) nonexisting directory
>>> write(sample_buildout, 'buildout.cfg',
... """
... [buildout]
... parts = javaproject
...
... [javaproject]
... recipe = collective.recipe.ant
... classpath = %s
... ant-options =
... echo
... -buildfile %s
...
... """ % (join(dirname(__file__), '__bogus__dir__'),
... buildfile))
>>> print system(buildout)
While:
Installing.
Getting section javaproject.
Initializing part javaproject.
Error: Classpath .../__bogus__dir__ does not exist.
<BLANKLINE>
Changelog
*********
0.1 (2008-01-20)
================
- Initial release.
Contributors
***********************
Kai Lautaportti (dokai), Author - kai.lautaportti@hexagonit.fi
Tom Gross - tom@toms-projekte.de
Download
***********************
Metadata
Release files for collective.recipe.ant 0.1dev-r57213
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 |
|---|---|---|---|---|
| collective.recipe.ant-0.1dev-r57213.tar.gz | 6.1 kB | Without provenance | Details for collective.recipe.ant-0.1dev-r57213.tar.gz |
Release files / collective.recipe.ant-0.1dev-r57213.tar.gz
| Download URL | collective.recipe.ant-0.1dev-r57213.tar.gz |
|---|---|
| Size | 6.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f32762ae5dab67bd146a405196e3a822eeb1074b5ac9a1d148ecd372d0f6052f
|
|
BLAKE2b-256 checksum How to use checksums |
380209752b4ee28b29ea6ed60c4a26d32b3391ac2980fbd79dfbda62dde7f87e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for collective.recipe.ant 0.1dev-r57213
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.