301 Moved Permanently

The release you want is at Codeberg.org.

3.0.0-beta7

(The beta6 release never actually got published because I forgot to tag it.)

1. Fixed issue #532. Make sure that user-supplied values for static options are used during compilation.

2. Refactored the paged media steps into the main build. Along the way, I discovered that Prince XML has an artifact in Maven Central, so I switched to that API. The available options for the Prince XML-backed p:css-formatter step have changed; some of those changes are backwards incompatible.

3. Restructured code and tests for running in a set of Docker containers. The idea is to be able to run testing and release tasks in containers so that there’s no “bleed through” of the local development environment.

4. Moved to the new Maven Central repository using the legacy OSSRH APIs.

3.0.0-beta5

1. Fixed issue #521. Make sure that static options are evalated with the correct context.

2. Fixed issue #519. Handle the case where the only command given is “info”.

3. Re-re-fixed issue #321. Once again, the problem was in the XInclude processor, now bumped to version 5.4.1. This time I wrote a fairly extensive test case to “prove” it works correctly.

3.0.0-beta4

1. Fixed issue #515. Allow (API) users to add custom Saxon configurers with XmlCalabashBuilder.

2. Fixed issue #513. Reverted the fix that added a warning message about non-node inputs to p:xslt. It was unreliable.

3. Fixed issue #509. Added an info command that can display information about the known mimetypes.

4. Fixed issue #508. Added .xqm, .xquery, and .xql as standard filename extensions for application/xquery files.

3.0.0-beta3

I wasn’t really planning to do another release today, but there are some nice usability improvements in here and releases are cheap…

1. Fixed issue #504. Improved the error messages reported when stylesheet compilation fails for a p:xslt step.

2. Fixed issue #498. Allow the port name to be omitted for input and output ports on the command line if the pipeline has only a single such port.

3. Fixed issue #499. Fixed a bug where the serialization option on the p:store step was not taking precedence.

4. Fixed issue #497. If you attempt to process a stylesheet without passing an initial template name, and if the input is not a node, it will often silently fail. Output a debug message warning of this fact.

5. Fixed issue #496. Improved the error message associated with a p:pipe as a child of p:input.

6. Fixed issue #493. Fixed the error location for dynamic errors in atomic steps. (Previously, the location of the containing compound step was always reported.)

3.0.0-beta2

1. Fixed issue #488. Make sure that the document manager is used as the resource resolver for step processing.

2. Fixed issue #485. Make sure that the global context item, and other properties, are correctly reset when p:xslt is used in a loop.

3. Fixed issue #483. Support constructing a pipeline from a java.xml.transform.Source.

4. Support XML input to the cx:selenium step. Also did some IDE-directed code cleanup in the step itself. There’s a (currently undocumented) RELAX NG grammar for the XML input. It’s possibly a bit sketchy. And the step doesn’t validate the input.

5. Fixed issue #478. Improved the error message associated with attempts to connect to an unknown port.

6. Fixed issue #476. Make sure that options are set to their typed values.

7. Fixed issue #474. Apply serialization properties specified in the configuration file.

8. Fixed issue #472. Fixed a bug where “null” would sometimes appear in the graph visualization.

9. Fixed issue #321 (again). Updated the XInclude processor to 5.4.0 to correct a bug where nested base URIs were not correctly preserved.

3.0.0-beta1

If I’m going to get a couple of betas out in May, I best get started, eh?

1. Fixed issue #466. The xsl:messages from stylesheets run with p:xslt are output at “info” level. (They were accidentally getting discarded in the last few alphas.)

2. Fixed issue #462. Make sure that option shortcut values are stored as untyped atomic values so that they can be promoted to the appropriate type.

3. Fixed issue #460. Refactored build and configuration APIs.

4. Fixed issue #456. Removed some debugging code that always printed a JVM stack trace when p:run failed.

5. Fixed issue #455. Refactored the DocumentManager API.

6. Added cx:jsonpath and cx:find extension steps.

7. Added cx:json-diff and cx:json-patch extension steps.

8. Made a number of improvements to error reporting.

• Improved error messages for documents that can’t be parsed. (Previously, “file not found” would be reported in some circumstances.)

• Improved error message when content type shortcuts are used in inappropriate places.

• Fixed a bug where the underlying cause of an exception sometimes got lost in nested exceptions. When a pipeline fails, the error report now includes the chain of causes.

• Clarified the error message for the special case of empty sequence in a type conversion error.

• Added a --stacktrace option to enable stack (step) traces in errors (and disabled them by default).

• Improved the formatting of error explanations when the --explain option is used.

3.0.0-alpha33

1. Fixed issue #450. Make sure that options passed on the command line are promoted as required. (So “true” can be used for an xs:boolean value.) Also changed the error code used for option values that don’t match (or can’t be promoted to) the correct type. They now raise err:XD0036 instead of err:XS0077 which is really about attribute values not option values.

2. Fixed issue #447. Make sure the default verbosity is “info”, not “warn”. (This error was introduced while tinkering with the logging code; it was probably never released.)

3. Fixed issue #441. Restore loading ~/.xmlcalabash3 as the default configuration file if no configuration is given explicitly and if ./.xmlcalabash3 doesn’t exist. (In alpha31 or alpha32, the code to load ~/.xmlcalabash3 was lost, now it’s back.)

4. Disabled standard Java logging to stderr. This seems a bit odd, but XML Calabash has its own error reporter (necessary so that pipelines and integrators can capture the error messages). That reporter sends all messages to the standard Java logging system. That’s necessary so that it’s possible to capture lower level debug messages to a file without sending them all to the console. But it means that if an error occurs, the reporter prints the error message and then the underlying Java logging system prints it again, in a slightly different format. That’s going to be both confusing and annoying, so by default no Java log messages are printed.

3.0.0-alpha32

1. Significant refactoring of message and logging systems.

There’s more separation between things that are logged through the message reporter and things that are only logged to the underlying Java logger. The intent is that things only relevant to debugging XML Calabash go only to the logger. Things that might be relevant to debugging a pipeline go to both places.

One exception is that details about how the application is configured go only to the underlying Java logger. This is necessary because we haven’t configured a message reporter before we’ve configured the application!

The default logback.xml configuration file has been simplified. It no longer uses dynamic configuration. Use a different configuration file to change the level.

The error explanation implementation has been changed so that it also uses the message reporter, rather than writing directly to stderr.

2. Multithreaded execution complicates the task the visualizer is trying to perform. The “detail” visualizer has been updated.

3. Fixed a few bugs in the cx:wait-for-update step; it didn’t work reliably for HTTP URIs.

3.0.0-alpha31

1. Fixed issue #434. Improved the conformance of p:import-functions. Private functions are now excluded and nested imports are handled correctly.

2. Fixed issue #431. Corrected errors in p:os-exec. Fixed the bug where output to stdout was discarded unless the process ended with a return code of zero. Serialization properties and output charsets are now handled correctly.

3. Fixed issue #427. Remove carriage returns from p:os-exec output on Windows.

4. Fixed issue #425. The cwd option on p:os-exec is handled correctly if it’s a URI.

5. Fixed issue #424. Reworked the DocumentManager API.

6. Fixed issue #258. Added support for the language attribute on the XVRL schema element.

7. XML Calabash now uses Saxon 12.6 by default.