Release of jpylyzer 1.14.1
Following a year of limited development activity, we proudly present jpylyzer 1.14.1. Here’s an overview of the most noticeable changes in this version.
Improved XML output
Jpylyzer’s output now contains a namespace declaration as well as a reference to an XSD schema. The schema can be found here. Hopefully these improvements will make post-processing jpylyzer’s output easier. Note that the schema has had limited testing so far, and it’s not inconceivable that it may need further tweaking. If you get unexpected results (e.g. output files that are not valid against the schema) please let us know, preferably using the issue tracker.
Recursive scanning of directory trees
--recurse option allows you to recursively scan a directory tree. Read this warning before using this feature; for operational production settings it’s probably safer not to use it yet. Thanks go out to Adam Retter, Jaishree Davey and Laura Damian of The National Archives (UK) who submitted this feature.
User Manual changes
The User Manual is now accessible in two ways:
as a downloadable self-contained HTML file. This file is completely self-contained (all style sheets, images, etc. are embedded in one single file), which makes it suitable for offline viewing. This replaces the former PDF version, which is now discontinued. (With the source of the User Manual now being in MarkDown, generating PDF derivatives of acceptable quality turned out to be too much hassle.) Both versions are generated from the MarkDown source with this little script.
CLI argument parser fix
The helper message in the latest versions of jpylyzer was somewhat confusing because the argument parser library was called in an unusual way. This has also been fixed (jpylyzer’s behavior is unaffected by this).
Vagrant virtual machine definitions and build scripts
Apart from the above changes, this release includes various minor tweaks, clean-ups and fixes; most of these are unnoticeable to the user.
It’s always possible that changes cause things to go wrong unintentionally; if this happens please get in touch, if possible using the issue tracker. Meanwhile, happy jpylyzing!