Found in an internal build run, showing up as:
svn2cl --reparagraph --stdout --include-rev -r HEAD:6087
runtime error: file /etc/svn2cl/svn2cl.xsl line 432 element param
xsltApplyXSLTTemplate: A potential infinite template recursion was detected.
You can adjust xsltMaxDepth (--maxdepth) in order to raise the maximum number of nested template calls and variables/params (currently set to 3000).
[...]
several times and tons of additional confused error output.
If we have UNRELEASED in the changelog the version number
should not be increased since the version has not been
released yet. Otherwise we'd have a version number in the
autobuild/snapshot version which is higher than the one
that has been officially relased.
${WORKSPACE}/binaries/: we want to separate sources and binaries
so we don't conflict with each other. Therefore put the files we
get from cowbuilder into ${WORKSPACE}/binaries/
remove files of previous runs: we get rid of source files from
previous runs, since Copy Artifact Plugin copies files but if
building fails we find multiple versions inside the workspace.
Since we might want to build older versions as well there is no
simple heuristic we could rely on, therefore get rid of old
files.
handle missing packages: When source package "foo" provides
binary packages "bar" and "baz" in version 0.23 but version 0.42
doesn't provide "baz" any longer, then the no-longer-present
binary package "baz" will stay in the archive since it's not
longer listed in 0.42. In case we even build an version older
than 0.23 providing baz then adding the package will fail at all.
Therefore we get rid of binary packages from the archive that are
no longer build by the current version.
Build-Depend on shunit2 since an according test script
verifies that all supported version numbers work as
intended.
generate-svn-snapshot has been adapted to use
increase-version-number accordingly.
Michael Prokop