From d7fb43d84d16bfecbae092def69ec0cfeb9ad697 Mon Sep 17 00:00:00 2001 From: jstaerk Date: Thu, 12 May 2022 12:30:02 +0200 Subject: [PATCH] updated release documentation and history --- History.md | 9 +++++++-- doc/development_documentation.md | 2 +- 2 files changed, 8 insertions(+), 3 deletions(-) diff --git a/History.md b/History.md index bcadd643..2b1de51e 100644 --- a/History.md +++ b/History.md @@ -1,6 +1,11 @@ +2.5.1 +======= +2022-05-12 + - upgraded en16931 validation to 1.3.8 -- Be able to embed Cross Industry Delivery Advice -- update xr to v. 2.2 +- Be able to embed/write/read Cross Industry Delivery Advice https://www.gs1-germany.de/gs1-standards/umsetzung/fachpublikationen/detailansicht/der-digitale-lieferschein-dls-die-digitale-abloesung-des-papier-lieferscheins/ +- Be able to write UBL 1Lieferschein https://www.bobbie.de/maschinenraum/1lieferschein +- update xr to v. 2.2 (mandatory as of August) - logging output now stderr again, since 2.4.0 it had mistakenly been on stdout 2.5.0 diff --git a/doc/development_documentation.md b/doc/development_documentation.md index aaf4bd31..04a328f2 100644 --- a/doc/development_documentation.md +++ b/doc/development_documentation.md @@ -176,7 +176,7 @@ Change to the project directory and run * `mvn clean install` confirm javadoc is OK with * `mvn javadoc:javadoc`. If that works you can * clean the release with `mvn release:clean` and prepare the release with - * `mvn release:prepare -DignoreSnapshots=true` and enter the version numbers. + * `mvn release:prepare` and enter the version numbers. * After that is through you can create a new release via `mvn release:perform`.This will also update the maven repo. ![screenshot](development_documentation_screenshot_release.png "Screenshot Release")