v1.2.1

This release includes mapping updates and sonar cloud fixes

Stories:

• MODGOBI-49 Sonar cloud security fix
• MODGOBI-48 Make location repeatable
• MODGOBI-46 Property name change in composite_purchase_order.json schema
• MODGOBI-42 Mapping Remaining fields for default mapping

v1.1.0 - Updating orders Interface versions

Updating the Orders dependency to align with latest release 2.0. Also contains updates to point to the latest acq-models with Renewal and Metadata changes

v1.0.1

Use the latest GOBI schema MODGOBI-39(https://issues.folio.org/browse/MODGOBI-39)
cache/reuse Mapping POJO MODGOBI-36(https://issues.folio.org/browse/MODGOBI-36)
Integrate with Latest acquisition schemas MODGOBI-33(https://issues.folio.org/browse/MODGOBI-33)
Ability to have default/fallback configurations MODGOBI-30(https://issues.folio.org/browse/MODGOBI-30)
Retrieve Mapping Configurations from Mod-configuration MODGOBI-8(https://issues.folio.org/browse/MODGOBI-8)
Requires locations interface 2.1 or 3.0
MODGOBI-28
MODGOBI-27
MODGOBI-26
MODGOBI-24
MODGOBI-23
MODGOBI-22
MODGOBI-19
MODGOBI-17
MODGOBI-15
MODGOBI-14
MODGOBI-10
MODGOBI-9
MODGOBI-7
MODGOBI-4
MODGOBI-3
MODGOBI-2
Added the GOBI PurchaseOrder.xsd for validation and code generation. Currently, we cannot use the XSD file in the RAML file due to RMB using a JSON unmarshaller instead of XML. The "model" code is generated by a JAXB maven plugin.
Added the acq-models submodule and generate "model" code for the necessary schemas, namely CompositePurchaseOrder and CompositePoLine. This code is generated by the jsonschema2pojo maven plugin due to a limitation of RMB that doesn't support generation of pojos for schemas that aren't consumed or produced by a RAML endpoint.
Updated the test data w/ actual requests placed by GOBI in the qa env during BAT.
Initial work