Release 1.0.1

.circleci/config.yml

@@ -0,0 +1,67 @@
+version: 2.1
+orbs:
+  gh: circleci/github-cli@2.1.0
+
+workflows:
+  version: 2
+  pr_build:
+    when:
+      not:
+        or:
+          - equal: [ dev, << pipeline.git.branch >> ]
+          - equal: [ master, << pipeline.git.branch >> ]
+    jobs:
+      # Performs a verify build for PRs
+      - validate:
+          context:
+            - Non-sensitive Env Vars
+      - maven_verify:
+          context: Non-sensitive Env Vars
+          requires:
+            - validate
+
+  stage_or_release_build:
+    when:
+      or:
+        - equal: [ dev, << pipeline.git.branch >> ]
+        - equal: [ master, << pipeline.git.branch >> ]
+    jobs:
+      # Deploys to maven central for dev (snapshot) and master builds
+      - validate:
+          context:
+            - Non-sensitive Env Vars
+      - maven_deploy:
+          context: 
+            - Open Source Release Credentials
+            - Non-sensitive Env Vars
+          requires:
+            - validate
+
+jobs:
+  validate:
+    machine:
+      image: ubuntu-2204:2023.02.1
+    steps:
+      - checkout
+      - run: 
+          name: "List installed packages"
+          command: apt list --installed
+      - run:
+          name: "Validate build"
+          command: source Infrastructure/Build-Scripts/validate_build.sh
+  maven_verify:
+    machine:
+      image: ubuntu-2204:2023.02.1
+    steps:
+      - checkout
+      - run:
+          name: "Perform Maven Verify"
+          command: source Infrastructure/Build-Scripts/mvn_verify.sh
+  maven_deploy:
+    machine:
+      image: ubuntu-2204:2023.02.1
+    steps:
+      - checkout
+      - run:
+          name: "Deploy to Maven Central"
+          command: source Infrastructure/Build-Scripts/mvn_deploy.sh

.github/dependabot.yml

@@ -0,0 +1,8 @@
+version: 2
+updates:
+  - package-ecosystem: maven
+    directory: "/"
+    schedule:
+      interval: "weekly"
+      day: "sunday"
+      time: "17:00"

.github/pull_request_template.md

@@ -0,0 +1,29 @@
+### Description of Changes
+
+What has been changed? If this is more than bug fixes we should consider incrementing the minor 
+version number. For non backwards compatible changes we need to increment the major version number.
+
+### Documentation
+
+Provide links to all relevant documentation that should be updated before asking for the PR to be reviewed. If this section is not relevant please write 'Not Applicable' rather than deleting the section.
+
+### Risks & Impacts
+
+The potential risks of this change as a bullet pointed list and how it might impact the wider sdk. Please consider how easily it would be to rollback these changes if they cause problems. Are there breaking changes?
+
+### Testing
+
+How have the changes been tested and the potential risks mitigated?
+
+### Compare (For layered PRs)
+
+Generate compare URL from https://github.com/ebx/ebx-structuredlogging-sdk/compare so that it's easily accessible. This is ONLY REQUIRED FOR COMPLICATED, DEPENDENT OR LAYERED PRs. Feel free to delete this section if not required.
+
+## Final Checklist
+
+Please tick once completed.
+
+- [ ] Build passes.
+- [ ] Versioning considered (the version number in this PR is inline with semantic 
+versioning requirements).
+- [ ] Change log has been updated.

.gitignore

@@ -21,3 +21,8 @@
 
 # virtual machine crash logs, see http://www.java.com/en/download/help/error_hotspot.xml
 hs_err_pid*
+
+/bin/
+/target/
+.idea/
+*.iml

.maven.xml

@@ -0,0 +1,23 @@
+<settings xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://maven.apache.org/SETTINGS/1.0.0" xsi:schemalocation="http://maven.apache.org/SETTINGS/1.0.0 http://maven.apache.org/xsd/settings-1.0.0.xsd">
+  <servers>
+    <server>
+      <!-- Maven Central Deployment -->
+      <id>ossrh</id>
+      <username>${env.SONATYPE_USERNAME}</username>
+      <password>${env.SONATYPE_PASSWORD}</password>
+    </server>
+  </servers>
+
+  <profiles>
+    <profile>
+      <id>ossrh</id>
+      <activation>
+        <activeByDefault>true</activeByDefault>
+      </activation>
+      <properties>
+        <gpg.executable>${env.GPG_EXECUTABLE}</gpg.executable>
+        <gpg.passphrase>${env.GPG_PASSPHRASE}</gpg.passphrase>
+      </properties>
+    </profile>
+  </profiles>
+</settings>

CHANGELOG.md

@@ -0,0 +1,9 @@
+# ebx-structuredlogging-sdk Changelog
+
+## 1.0.0 (Jan 1, 2014)
+
+* Initial release
+
+## 1.0.1 (May 16, 2024)
+
+* Update dependencies and add dependabot configuration.

CONTRIBUTING.md

@@ -0,0 +1,37 @@
+# Contributing to ebx-structuredlogging-sdk
+
+Contributing code is an essential part of open source and we try to make this as easy as possible. There are several ways you can contribute to ebx-structuredlogging-sdk.  Here are some guidelines for creating new issues and sending us pull requests. Please read them carefully before contributing.
+
+## How to create a new issue
+
+We like new issues and are very keen to hear your problems, ideas and proposals. After analyzing them, they are categorized and assigned to a milestone. To make this part easier you should give us some information. Please read the checklist and try to mark as many entries as possible.
+
+**Issue checklist:**
+* Check the closed issues and don't open duplicates
+* Explain your idea or problem in plain English
+* Provide a JSON snippet if possible (values may be obfuscated but similar to the original)
+* Tell us why this is beneficial and what the advantage is for the users
+* Explain your use case, it's easier to understand a proposal if we have some background knowledge
+
+## How to create a pull request
+
+Pull requests (PR) are a very important way to contribute code to the library. We have guidelines for sending us a PR, because changes to the source code are even more fundamental than sending a new issue. This is an overview of our prerequisites.
+
+**PR checklist:**
+* Please ensure you have an associated [github issue](https://github.com/ebx/ebx-structuredlogging-sdk/issues) to hand, this needs to be included in the PR. If a suitable issue doesn't already exist feel free to create one, as described above.
+* The code must be formatted with our code formatter (have a look at the [CodeStyle folder](https://github.com/ebx/ebx-structuredlogging-sdk/tree/master/CodeStyle)). If you perform a local *mvn verify* before creating the PR your changes will already be getting validated for style.
+* The code layout should conform to our general design standards (if you feel it's necessary to go against the grain, please ask us first!).
+* You should complete the PR template and please format your PR title as follows:
+
+        GH-[Issue#] [Summary of change or issue title]
+
+  for example:
+
+        GH-123 Fixed NPE exception when resvoling an organisation
+
+* The pull request should be mergeable, i.e. no conflicts.
+* Junit tests required for any functional change must be included.
+* The pull request should be targetted at the `dev` branch. If you raise it against `master` the PR will fail to build.
+* Please try to keep PR commits in a logical order incase we need to review each commit seperately, but generally speaking the fewer commits the better.
+* Your PR will have to build succesfully against our CI (we use [Travis CI](https://travis-ci.org/ebx/ebx-structuredlogging-sdk)).
+* **Important Note**: If your PR contains breaking changes you must include a MAJOR version bump in the PR.

CodeStyle/Eclipse_EBX_Code_Style_Imports.importorder

@@ -0,0 +1,11 @@
+#Organize Import Order
+#Tue Apr 05 15:57:16 BST 2016
+7=java
+5=sun
+6=io
+4=org
+3=net
+2=mockit
+1=com
+0=sh
+8=javax