Skip to content

GitLab

A
assert-object-equals-module
Commit 7055a58a authored by Danijel Dragicevic's avatar Danijel Dragicevic
Browse files
Options

Add LICENSE

parent ffa304e0
Pipeline #72392 passed with stages
      in 1 minute and 39 seconds
      Expand all Show whitespace changes
      Inline Side-by-side
      Showing with 698 additions and 15 deletions
      .gitlab-ci.yml 0 → 100644
      View file @ 7055a58a
      image: maven:latest
      variables:
      MAVEN_CLI_OPTS: "-s .m2/settings.xml --batch-mode"
      MAVEN_OPTS: "-Dmaven.repo.local=.m2/repository"
      cache:
      paths:
      - .m2/repository/
      - target/
      build:
      stage: build
      script:
      - mvn $MAVEN_CLI_OPTS compile
      test:
      stage: test
      script:
      - mvn $MAVEN_CLI_OPTS test
      deploy:
      stage: deploy
      script:
      - mvn $MAVEN_CLI_OPTS deploy
      only:
      - master
      \ No newline at end of file
      .m2/settings.xml 0 → 100644
      View file @ 7055a58a
      <settings xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.1.0 http://maven.apache.org/xsd/settings-1.1.0.xsd"
      xmlns="http://maven.apache.org/SETTINGS/1.1.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
      <servers>
      <server>
      <id>central</id>
      <username>${env.MAVEN_REPO_USER}</username>
      <password>${env.MAVEN_REPO_PASS}</password>
      </server>
      </servers>
      </settings>
      \ No newline at end of file
      LICENSE 0 → 100644
      View file @ 7055a58a
      This diff is collapsed.
      README.md
      View file @ 7055a58a
      ......@@ -5,29 +5,42 @@ Mule 4.x (tested on 4.1.4 version)
      In case you are working with Mule 3.x, have a look [here](https://github.com/rbutenuth/assert-object-equals-connector), there you find a version suitable for Mule 3.
      ## Installation
      For beta connectors you can download the source code and build it with Maven (mvn clean install).
      Then you can add it to Studio by adding the following dependency to your project:
      ```
      <groupId>de.codecentric.mule.modules</groupId>
      <artifactId>assert-object-equals-module</artifactId>
      <version>1.0.180-SNAPSHOT</version>
      <classifier>mule-plugin</classifier>
      To install this module via Maven, please add following repository and dependency to yur pom.xml file
      ```xml
      <repository>
      <id>central</id>
      <name>artifactory.codecentric.de-releases</name>
      <url>https://artifactory.codecentric.de/artifactory/public</url>
      </repository>
      <dependency>
      <groupId>de.codecentric.mule.modules</groupId>
      <artifactId>assert-object-equals-module</artifactId>
      <version>1.1.0</version>
      <classifier>mule-plugin</classifier>
      </dependency>
      ```
      ## Usage
      Documentation will be released soon.
      The connector can be used for Object structures or XML:
      ## CI
      * [Object structures and JSON](../docs/compare-objects.md)
      * [XML](../docs/compare-xml.md)
      Will be added later....
      ## Mule example app
      ## Maven Site
      Mule 4 example application can be checked out here:
      * https://gitlab.codecentric.de/danijel.dragicevic/assert-object-equal-module-mule-app-example
      ## CI
      Will be added later....
      Pipelines for this project:
      * https://gitlab.codecentric.de/danijel.dragicevic/assert-object-equals-module/pipelines?scope=branches&page=1
      ## Reporting Issues
      We use GitLab: Issues for tracking issues with this connector. You can report new issues at this link https://gitlab.codecentric.de/danijel.dragicevic/assert-object-equals-module/issues.
      \ No newline at end of file
      We use GitLab Issues for tracking issues with this connector. You can report new issues at this link:
      * https://gitlab.codecentric.de/danijel.dragicevic/assert-object-equals-module/issues.
      \ No newline at end of file
      docs/compare-objects.md 0 → 100644
      View file @ 7055a58a
      # Comparing Objects (or JSON)
      The object comparison is 'hand written' and not based on an existing library. So be careful, there may be bugs. :-)
      It can be used to compare object structures the way Mule uses, nested Java `List` and `Map` (or anything else with
      a meaningful `equals()` methods, but for this you don't need this connector).
      The actual value and the comparison value (called expected) can be provided as object structure or in one of the follogin ways:
      * InputStream
      * byte[]
      * OutputHandler (returned by DataWeav with mode="deferred")
      * String starting with `[` or `{`
      All these will be converted to an object structure by `org.codehaus.jackson.map.ObjectMapper`. Since version 1.0.0 the operation does no longer return the parsed object, it now returns the input object (in case of InputStream/OutputHandler: A copy because the stream has to be read to do the comparison).
      The test for equality will drill down the object structure:
      * `null` equals `null`
      * Two maps are equal when they contain the same key set and the mapping is equal for map entries with the same key in the two maps.
      * Two lists are equal when they have the same size and elements with same index are equal in the two lists.
      * Other objects are equal according their `equals()` method.
      ## Options
      There are three options to tweak the comparison. They can be set globally (two of them) or on sub trees:
      1. `contains_only_on_maps`: Two maps are considered equal, when the key set of the expected map is a subset of the key set of the actual map.
      (Of course, values must still be equal.) This option is useful when you want to check that some values are contained in the result.
      2. `check_map_order`: This confines the comparison of the key sets of map: They must be equal and in the same order. This makes
      no sense for `HashMap`, but for `LinkedHashMap` (which is used by Mule in a lots of places).
      3. `ignore`: The node is ignored in the comparison. Useful to exclude values like time stamps or sequence numbers from the comparison.
      For obvious reasons this option is not available on the global level.
      ## Path patterns
      When you want to apply one (or several) of this options to a subtree of the object structure, you have to specify the path to the subtree
      by one of the following patterns:
      * `?` (wildcard one): Matches one node in the tree (Map, List, leaf).
      * `*` (wildcard any): Matches a sequence of nodes (can be the empty sequence).
      * `[#]`: Matches a List element.
      * `[42]` Matches List element with index 42 (starting at 0).
      * `[-1]` Matches the last element in a List (-2 for the second last etc.).
      * `['foo']` Matches the Map entry `foo`. The String between the single quotes is a regular expression.
      * `['fo''o']` Matches the Map entry `fo'o` (example for quoting).
      * `['foo.*']` Matches all Map entries starting with `foo` (example for the regular expression feature).
      The path patterns can be combined, e.g.:
      ```['addresses'][#]['street']```
      Matches the node `street` for each address in a list of addresses in the node `addresses`.
      After the path pattern you can place one or several options shown above (separated by space).
      ## Examples
      So let's look at some examples. I have created two JSON documents:
      The expected JSON document:
      ```json
      {
      "name": "Peter Pan",
      "addresses": [
      {
      "timestamp": 4711,
      "street": "Elm Street",
      "city": "New York"
      },
      {
      "timestamp": 4712,
      "street": "Hochstraße",
      "city": "Solingen"
      }
      ],
      "profession": "Wizard"
      }
      ```
      The actual JSON document:
      ```json
      {
      "name": "Peter Pan",
      "profession": "Wizard",
      "addresses": [
      {
      "street": "Elm Street",
      "timestamp": 1234,
      "city": "New York"
      },
      {
      "timestamp": 1235,
      "street": "Hochstraße",
      "city": "Solingen"
      }
      ]
      }
      ```
      When you look at them closely, you will find some differences:
      1. The order of the top level object is different (addresses/profession)
      2. The timestamp in the addresses is different
      3. The order within the addresses objects is different
      Our first try will throw an `AssertionError` because of different timestamp values:
      ```xml
      <munit:test name="compare-person-fail-test" expectedException="java.lang.AssertionError" description="MUnit Test" >
      <munit:validation >
      <assertobjectequals:compare-objects
      expected="#[MunitTools::getResourceAsString('json/person-expected.json')]"
      actual="#[MunitTools::getResourceAsString('json/person-actual.json')]" >
      <assertobjectequals:path-options />
      </assertobjectequals:compare-objects>
      </munit:validation>
      </munit:test>
      ```
      I marked the exception as expected, so the test itself will be green. (Nobody likes red bars...)
      To make the object structures equal for this module, we have to exclude the timestamp from the comparison.
      The first way to do this is with an embedded object:
      ```xml
      <munit:test name="compare-person-success-1-test" description="MUnit Test" >
      <munit:validation >
      <assertobjectequals:compare-objects
      expected="#[MunitTools::getResourceAsString('json/person-expected.json')]"
      actual="#[MunitTools::getResourceAsString('json/person-actual.json')]">
      <assertobjectequals:path-options >
      <assertobjectequals:path-option value="['addresses'][#]['timestamp'] ignore" />
      </assertobjectequals:path-options>
      </assertobjectequals:compare-objects>
      </munit:validation>
      </munit:test>
      ```
      We can configure this in the GUI by clicking on the "Path patterns + options" drop-down menu and selecting "Edit inline" option.
      After that we have to click on green plus sign to add our path option. Popup window will open, and allow us to enter our value.
      See the picture bellow:
      ![Object Builder](../docs/images/object-builder.png)
      Another way is to express the list as a MEL expression:
      ```xml
      <munit:test name="compare-person-success-2-test" description="MUnit Test" >
      <munit:validation >
      <assertobjectequals:compare-objects
      expected="#[MunitTools::getResourceAsString('json/person-expected.json')]"
      actual="#[MunitTools::getResourceAsString('json/person-actual.json')]"
      pathOptions="#[[&quot;['addresses'][#]['timestamp'] ignore&quot;]]">
      </assertobjectequals:compare-objects>
      </munit:validation>
      </munit:test>
      ```
      How can we fail in a different way? Activate Map order checking:
      ```xml
      <munit:test name="compare-person-fail-map-order-test" description="MUnit Test" >
      <munit:validation >
      <assertobjectequals:compare-objects
      expected="#[MunitTools::getResourceAsString('json/person-expected.json')]"
      actual="#[MunitTools::getResourceAsString('json/person-actual.json')]"
      pathOptions="#[[&quot;['addresses'][#]['timestamp'] ignore&quot;]]"
      checkMapOrder="true">
      </assertobjectequals:compare-objects>
      </munit:validation>
      </munit:test>
      ```
      For a complete example of the test suite see [object-demos.xml](object-demos.xml).
      docs/compare-xml.md 0 → 100644
      View file @ 7055a58a
      # Comparing XML
      The XML comparison is based on [xmlunit](https://github.com/xmlunit/xmlunit), version 2.3.0.
      For the demos in this documentation, I provided the XML as String in MEL expressions. This works only for really small XML
      and the escaping of `<` and `>` makes it completely unreadable when you switch to the XML view in AnypointStudio.
      Fortunately, xmlunit is quite flexible when it comes to input sources: It can consume Strings (as in the examples), byte arrays, InputStreams,
      Files and some more sources. See [xmlunit documentation](https://github.com/xmlunit/user-guide/wiki/Providing-Input-to-XMLUnit) for details.
      If you have bigger XML documents, place them in `src/test/resources` and load them with `getResourceAsString(...)`, e.g. like this:
      ```txt
      "#[MunitTools::getResourceAsString('xml/simple-expected.xml')]"
      ```
      ## Simple example
      So let's start with a simple example to compare two XML Strings:
      ![xml-is-xml](../docs/images/xml-is-xml.png)
      As long as you ignore all the quoting, it's quite simple in XML, too:
      ```xml
      <munit:test name="compare-xml" description="Munit Test">
      <munit:validation >
      <assertobjectequals:compare-xml doc:name="xml is xml"
      expected="#['&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;&lt;a&gt;&lt;b&gt;&lt;/b&gt;&lt;/a&gt;']"
      actual="#['&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;&lt;a&gt;&lt;b&gt;&lt;/b&gt;&lt;/a&gt;']"
      xmlCompareOption="NORMALIZE_WHITESPACE">
      </assertobjectequals:compare-xml>
      </munit:validation>
      </munit:test>
      ```
      ## Handling whitespace and comments
      Usually we don't want to compare our XML documents character by character, otherwise we could just use the built in assert of MUnit.
      We can select between three modes of comparison:
      * NORMALIZE_WHITESPACE : Normalize Text-Elements by removing all empty text nodes and normalizing the non-empty ones.
      * IGNORE_WHITESPACE: Ignore whitespace by removing all empty text nodes and trimming the non-empty ones.
      * IGNORE_COMMENTS: Will remove all comment-Tags "<!-- Comment -->" from test- and control-XML before comparing.
      "normalized" in this context means all whitespace characters are replaced by space characters and consecutive
      whitespace characters are collapsed.
      For a complete example of the test suite see [xml-demos.xml](xml-demos.xml).
      docs/object-demos.xml 0 → 100644
      View file @ 7055a58a
      <?xml version="1.0" encoding="UTF-8"?>
      <mule
      xmlns:assertobjectequals="http://www.mulesoft.org/schema/mule/assertobjectequals"
      xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
      xmlns:munit="http://www.mulesoft.org/schema/mule/munit"
      xmlns:munit-tools="http://www.mulesoft.org/schema/mule/munit-tools"
      xmlns="http://www.mulesoft.org/schema/mule/core"
      xmlns:doc="http://www.mulesoft.org/schema/mule/documentation"
      xsi:schemaLocation="
      http://www.mulesoft.org/schema/mule/core http://www.mulesoft.org/schema/mule/core/current/mule.xsd
      http://www.mulesoft.org/schema/mule/munit http://www.mulesoft.org/schema/mule/munit/current/mule-munit.xsd
      http://www.mulesoft.org/schema/mule/munit-tools http://www.mulesoft.org/schema/mule/munit-tools/current/mule-munit-tools.xsd
      http://www.mulesoft.org/schema/mule/assertobjectequals http://www.mulesoft.org/schema/mule/assertobjectequals/current/mule-assertobjectequals.xsd">
      <munit:config name="object-demos" doc:name="Munit configuration" />
      <munit:test name="compare-strings-success-test" description="MUnit Test" >
      <munit:validation >
      <assertobjectequals:compare-objects doc:name="success (foo is foo)"
      expected="#['foo']"
      actual="#['foo']" >
      <assertobjectequals:path-options />
      </assertobjectequals:compare-objects>
      </munit:validation>
      </munit:test>
      <munit:test name="compare-strings-fail-test" expectedException="java.lang.AssertionError" description="MUnit Test">
      <munit:validation >
      <assertobjectequals:compare-objects doc:name="fails (foo is not bar)"
      expected="#['foo']"
      actual="#['bar']" >
      <assertobjectequals:path-options />
      </assertobjectequals:compare-objects>
      </munit:validation>
      </munit:test>
      <munit:test name="compare-expected-from-resource-test" description="MUnit Test" >
      <munit:validation >
      <assertobjectequals:compare-objects doc:name="success (foo is foo)"
      expected="#[MunitTools::getResourceAsString('json/simple-expected.json')]"
      actual="#['{&quot;foo&quot;: 42}']" >
      <assertobjectequals:path-options />
      </assertobjectequals:compare-objects>
      </munit:validation>
      </munit:test>
      <munit:test name="compare-person-fail-test" expectedException="java.lang.AssertionError" description="MUnit Test" >
      <munit:validation >
      <assertobjectequals:compare-objects doc:name="fails (timestamp)"
      expected="#[MunitTools::getResourceAsString('json/person-expected.json')]"
      actual="#[MunitTools::getResourceAsString('json/person-actual.json')]" >
      <assertobjectequals:path-options />
      </assertobjectequals:compare-objects>
      </munit:validation>
      </munit:test>
      <munit:test name="compare-person-success-1-test" description="MUnit Test" >
      <munit:validation >
      <assertobjectequals:compare-objects doc:name="success (options in object)"
      expected="#[MunitTools::getResourceAsString('json/person-expected.json')]"
      actual="#[MunitTools::getResourceAsString('json/person-actual.json')]">
      <assertobjectequals:path-options >
      <assertobjectequals:path-option value="['addresses'][#]['timestamp'] ignore" />
      </assertobjectequals:path-options>
      </assertobjectequals:compare-objects>
      </munit:validation>
      </munit:test>
      <munit:test name="compare-person-success-2-test" description="MUnit Test" >
      <munit:validation >
      <assertobjectequals:compare-objects doc:name="success (options in MEL)"
      expected="#[MunitTools::getResourceAsString('json/person-expected.json')]"
      actual="#[MunitTools::getResourceAsString('json/person-actual.json')]"
      pathOptions="#[[&quot;['addresses'][#]['timestamp'] ignore&quot;]]">
      </assertobjectequals:compare-objects>
      </munit:validation>
      </munit:test>
      <munit:test name="compare-person-fail-map-order-test" expectedException="java.lang.AssertionError" description="MUnit Test" >
      <munit:validation >
      <assertobjectequals:compare-objects doc:name="success (options in object)"
      expected="#[MunitTools::getResourceAsString('json/person-expected.json')]"
      actual="#[MunitTools::getResourceAsString('json/person-actual.json')]"
      pathOptions="#[[&quot;['addresses'][#]['timestamp'] ignore&quot;]]"
      checkMapOrder="true">
      </assertobjectequals:compare-objects>
      </munit:validation>
      </munit:test>
      <munit:test name="compare-person-fail-contains-only-on-maps-test" expectedException="java.lang.AssertionError" description="MUnit Test" >
      <munit:validation >
      <assertobjectequals:compare-objects doc:name="success (options in object)"
      expected="#[MunitTools::getResourceAsString('json/person-extended.json')]"
      actual="#[MunitTools::getResourceAsString('json/person-actual.json')]"
      containsOnlyOnMaps="true">
      <assertobjectequals:path-options />
      </assertobjectequals:compare-objects>
      </munit:validation>
      </munit:test>
      </mule>
      docs/xml-demos.xml 0 → 100644
      View file @ 7055a58a
      <?xml version="1.0" encoding="UTF-8"?>
      <mule
      xmlns:assertobjectequals="http://www.mulesoft.org/schema/mule/assertobjectequals"
      xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
      xmlns:munit="http://www.mulesoft.org/schema/mule/munit"
      xmlns:munit-tools="http://www.mulesoft.org/schema/mule/munit-tools"
      xmlns="http://www.mulesoft.org/schema/mule/core"
      xmlns:doc="http://www.mulesoft.org/schema/mule/documentation"
      xsi:schemaLocation="
      http://www.mulesoft.org/schema/mule/core http://www.mulesoft.org/schema/mule/core/current/mule.xsd
      http://www.mulesoft.org/schema/mule/munit http://www.mulesoft.org/schema/mule/munit/current/mule-munit.xsd
      http://www.mulesoft.org/schema/mule/munit-tools http://www.mulesoft.org/schema/mule/munit-tools/current/mule-munit-tools.xsd
      http://www.mulesoft.org/schema/mule/assertobjectequals http://www.mulesoft.org/schema/mule/assertobjectequals/current/mule-assertobjectequals.xsd">
      <munit:config name="xml-demos" doc:name="Munit configuration" />
      <munit:test name="compare-xml-success-test" description="Munit Test">
      <munit:validation >
      <assertobjectequals:compare-xml doc:name="success (xml is xml)"
      expected="#['&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;&lt;a&gt;&lt;b&gt;&lt;/b&gt;&lt;/a&gt;']"
      actual="#['&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;&lt;a&gt;&lt;b&gt;&lt;/b&gt;&lt;/a&gt;']"
      xmlCompareOption="NORMALIZE_WHITESPACE">
      </assertobjectequals:compare-xml>
      </munit:validation>
      </munit:test>
      <munit:test name="compare-xml-fail-test" expectedException="java.lang.AssertionError" description="Munit Test">
      <munit:validation >
      <assertobjectequals:compare-xml doc:name="fails (xml is not other xml)"
      expected="#['&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;&lt;a&gt;&lt;b&gt;ABBA&lt;/b&gt;&lt;/a&gt;']"
      actual="#['&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;&lt;a&gt;&lt;b&gt;AB BA&lt;/b&gt;&lt;/a&gt;']"
      xmlCompareOption="NORMALIZE_WHITESPACE">
      </assertobjectequals:compare-xml>
      </munit:validation>
      </munit:test>
      <munit:test name="compare-expected-xml-from-resource-test" description="Munit Test">
      <munit:validation >
      <assertobjectequals:compare-xml doc:name="success (xml is xml)"
      expected="#['&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;&lt;a&gt;&lt;b&gt;ABBA&lt;/b&gt;&lt;/a&gt;']"
      actual="#[MunitTools::getResourceAsString('xml/simple-expected.xml')]"
      xmlCompareOption="NORMALIZE_WHITESPACE">
      </assertobjectequals:compare-xml>
      </munit:validation>
      </munit:test>
      <munit:test name="compare-xml-whitespace-success-test" description="Munit Test">
      <munit:validation >
      <assertobjectequals:compare-xml doc:name="success (xml is xml)"
      expected="#['&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;&lt;a&gt;&lt;b&gt;AB BA&lt;/b&gt;&lt;/a&gt;']"
      actual="#['&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;&lt;a&gt;&lt;b&gt;AB BA&lt;/b&gt;&lt;/a&gt;']"
      xmlCompareOption="NORMALIZE_WHITESPACE">
      </assertobjectequals:compare-xml>
      </munit:validation>
      </munit:test>
      <munit:test name="compare-xml-whitespace-fail-test" expectedException="java.lang.AssertionError" description="Munit Test">
      <munit:validation >
      <assertobjectequals:compare-xml doc:name="fails (xml is not other xml)"
      expected="#['&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;&lt;a&gt;&lt;b&gt;AB BA&lt;/b&gt;&lt;/a&gt;']"
      actual="#['&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;&lt;a&gt;&lt;b&gt;AB BA&lt;/b&gt;&lt;/a&gt;']"
      xmlCompareOption="IGNORE_WHITESPACE">
      </assertobjectequals:compare-xml>
      </munit:validation>
      </munit:test>
      <munit:test name="compare-xml-comment-success-test" description="Munit Test">
      <munit:validation >
      <assertobjectequals:compare-xml doc:name="success (xml is xml)"
      expected="#['&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;&lt;a&gt;&lt;b&gt;&lt;/b&gt;&lt;/a&gt;']"
      actual="#['&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;&lt;a&gt;&lt;b&gt;&lt;!-- fancy comment --&gt;&lt;/b&gt;&lt;/a&gt;']"
      xmlCompareOption="IGNORE_COMMENTS">
      </assertobjectequals:compare-xml>
      </munit:validation>
      </munit:test>
      <munit:test name="compare-xml-comment-fail-test" expectedException="java.lang.AssertionError" description="Munit Test">
      <munit:validation >
      <assertobjectequals:compare-xml doc:name="fails (xml is not other xml)"
      expected="#['&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;&lt;a&gt;&lt;b&gt;&lt;/b&gt;&lt;/a&gt;']"
      actual="#['&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;&lt;a&gt;&lt;b&gt;&lt;!-- fancy comment --&gt;&lt;/b&gt;&lt;/a&gt;']"
      xmlCompareOption="NORMALIZE_WHITESPACE">
      </assertobjectequals:compare-xml>
      </munit:validation>
      </munit:test>
      </mule>
      pom.xml
      View file @ 7055a58a
      ......@@ -6,7 +6,7 @@
      <modelVersion>4.0.0</modelVersion>
      <groupId>de.codecentric.mule.modules</groupId>
      <artifactId>assert-object-equals-module</artifactId>
      <version>1.0.180-SNAPSHOT</version>
      <version>1.1.0</version>
      <packaging>mule-extension</packaging>
      <name>Assert Object Equals Extension</name>
      ......@@ -16,6 +16,22 @@
      <version>1.1.3</version>
      </parent>
      <developers>
      <developer>
      <name>Danijel Dragicevic</name>
      <organization>codecentric AG</organization>
      <organizationUrl>https://www.codecentric.de</organizationUrl>
      </developer>
      </developers>
      <licenses>
      <license>
      <name>Apache License, Version 2.0</name>
      <url>http://www.apache.org/licenses/LICENSE-2.0.txt</url>
      <distribution>repo</distribution>
      </license>
      </licenses>
      <dependencies>
      <dependency>
      <groupId>com.fasterxml.jackson.core</groupId>
      ......@@ -38,4 +54,12 @@
      <version>2.3.0</version>
      </dependency>
      </dependencies>
      <distributionManagement>
      <repository>
      <id>central</id>
      <name>artifactory.codecentric.de-releases</name>
      <url>${env.MAVEN_REPO_URL}/public</url>
      </repository>
      </distributionManagement>
      </project>
      Markdown is supported
      0% or
      You are about to add 0 people to the discussion. Proceed with caution.
      Finish editing this message first!
      Please register or to comment