Mustangserver 1.3.1

On July 23rd we released Mustangserver 1.3.1 with a improved documentation and better “Phive”-validation, i.e. Phive now also validates XRechnung 3.0.2 and FatturaPA, the number of supported format/version combinations (“VES-IDs”) has increated from 144 to 173.

Of course Mustangproject has been upgraded to 2.12 in the background, some smaller features were added and PDF/A-3 has now, additionally to PDF/A-1, become acceptable input.

Mustangserver 1.3.1 can be specifically selected and will become default for operations without specified versions at the next planned maintenance on 28 September. On the subsequent planned maintenance some three month later the pre-predecessor, Mustangserver 1.2.0, will likely be phased out.

Mustang 2.12.0

Today, on July 20th, 2024, we published Mustang 2.12.0. Due to dependencies, this is the first Mustang to require at least Java 11 (previously Java 8).

Fixes

  • set profile to XRechnung if XR is imported #395
  • #397 Build succeeds but file is unusable on alpine/docker
  • Fix #389: ClassCastException: ZUGFeRDExporterFromA3
  • ZF extended no longer requires deliverydate #411
  • ubl visualization: no longer require ubl namespace prefix #416
  • #392 CLI: action combine: –ignorefileextension to ignore PDF/A input file errors dosen’t work
  • Return all BankDetails from parsed CII xml: #408.

Refactorings

  • Jakarta XML support #372
  • Upgrade to PDFBox 3 #373
  • Requires Java 11 due to PH-Schematron 8
  • for CLI combine, fx is now default
  • logback (#402) and java.util.logging (#407) removed in favor of slf4j #402
  • Powershell compatibility: added –no-additional-attachments command line option for better batch processing:
    In cmd also –attachments “” worked but in powershell it was hard to figure out that one had to use –attachments ‘””‘

New features

  • support pdf export/visualization to PDF, thanks to Heavenfighter #387 allow embedd fonts from jar-file for pdf creation #388
  • Be able to validate XRechnung/UBL files #337

Postscriptum, July 22nd 8pm CET: While the change to Java 11 had been announced the need for the “shaded” classifier to include dependencies when deploying from Maven Central came surprisingly. Please let me know if you have an idea where that came from, I dont see changes that should have made that neccessary.