STTRS-1136 prepare to be open source

.github/workflows/ossrhDeploy.yml

@@ -0,0 +1,32 @@
+name: Publish package to the Maven Central Repository
+on:
+  release:
+    types: [created]
+jobs:
+  publish:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v2
+      - name: Set up Maven Central Repository
+        uses: actions/setup-java@v1
+        with:
+          java-version: 17
+          server-id: ossrh
+          server-username: MAVEN_USERNAME
+          server-password: MAVEN_PASSWORD
+      - id: install-secret-key
+        name: Install gpg secret key
+        run: |
+         cat <(echo -e "${{ secrets.OSSRH_GPG_SECRET_KEY }}") | gpg --batch --import
+         gpg --list-secret-keys --keyid-format LONG
+      - id: publish-to-central
+        name: Publish to Central Repository
+        env:
+          MAVEN_USERNAME: ${{ secrets.OSSRH_USERNAME }}
+          MAVEN_PASSWORD: ${{ secrets.OSSRH_PASSWORD }}
+        run: |
+          mvn \
+            --no-transfer-progress \
+            --batch-mode \
+            -Dgpg.passphrase=${{ secrets.OSSRH_GPG_SECRET_KEY_PASSWORD }} \
+            clean deploy

CHANGELOG.md

@@ -4,8 +4,26 @@ All notable changes to this project will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
-## Unreleased
-- STTRS-1127: support to send grouped multi response 
+## 5.0.0 - 2023-06-05
+### Changed
+- Support for spring 3
+- Rename packages caused by hand over to solace community
+
+### Added
+_n/a_
+
+### Removed
+- Support for spring 2
+
+## 4.0.0 - 2023-05-30
+### Changed
+_n/a_
+
+### Added
+- STTRS-1127: support to send grouped multi response
+
+### Removed
+_n/a_
 
 ## 3.4.0 - 2023-05-10
 ### Changed

CODE_OF_CONDUCT.md

@@ -0,0 +1,132 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our
+community a harassment-free experience for everyone, regardless of age, body
+size, visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socio-economic status,
+nationality, personal appearance, race, religion, or sexual identity
+and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming,
+diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our
+community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes,
+  and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the
+  overall community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or
+  advances of any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email
+  address, without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of
+acceptable behavior and will take appropriate and fair corrective action in
+response to any behavior that they deem inappropriate, threatening, offensive,
+or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject
+comments, commits, code, wiki edits, issues, and other contributions that are
+not aligned to this Code of Conduct, and will communicate reasons for moderation
+decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when
+an individual is officially representing the community in public spaces.
+Examples of representing our community include using an official e-mail address,
+posting via an official social media account, or acting as an appointed
+representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the community leaders responsible for enforcement at
+[email protected].
+All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the
+reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining
+the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed
+unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing
+clarity around the nature of the violation and an explanation of why the
+behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series
+of actions.
+
+**Consequence**: A warning with consequences for continued behavior. No
+interaction with the people involved, including unsolicited interaction with
+those enforcing the Code of Conduct, for a specified period of time. This
+includes avoiding interactions in community spaces as well as external channels
+like social media. Violating these terms may lead to a temporary or
+permanent ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including
+sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public
+communication with the community for a specified period of time. No public or
+private interaction with the people involved, including unsolicited interaction
+with those enforcing the Code of Conduct, is allowed during this period.
+Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community
+standards, including sustained inappropriate behavior,  harassment of an
+individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within
+the community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 2.0, available at
+[https://www.contributor-covenant.org/version/2/0/code_of_conduct.html][v2.0].
+
+Community Impact Guidelines were inspired by 
+[Mozilla's code of conduct enforcement ladder][Mozilla CoC].
+
+For answers to common questions about this code of conduct, see the FAQ at
+[https://www.contributor-covenant.org/faq][FAQ]. Translations are available 
+at [https://www.contributor-covenant.org/translations][translations].
+
+[homepage]: https://www.contributor-covenant.org
+[v2.0]: https://www.contributor-covenant.org/version/2/0/code_of_conduct.html
+[Mozilla CoC]: https://github.com/mozilla/diversity
+[FAQ]: https://www.contributor-covenant.org/faq
+[translations]: https://www.contributor-covenant.org/translations

CONTRIBUTING.md

@@ -0,0 +1,100 @@
+# How to contribute
+
+We'd love for you to contribute and welcome your help. Here are some guidelines to follow:
+
+- [Issues and Bugs](#issue)
+- [Submitting a fix](#submitting)
+- [Feature Requests](#features)
+- [Questions](#questions)
+
+## <a name="issue"></a> Did you find a issue?
+
+* **Ensure the bug was not already reported** by searching on GitHub under *Issues*
+
+* If you're unable to find an open issue addressing the problem, open a new one
+
+## <a name="submitting"></a> Did you write a patch that fixes a bug?
+
+Open a new GitHub pull request with the patch following the steps outlined below. Ensure the PR description clearly describes the problem and solution. Include the relevant issue number if applicable.
+
+Before you submit your pull request consider the following guidelines:
+
+* Search *Pull Requests* for an open or closed Pull Request
+  that relates to your submission. You don't want to duplicate effort.
+
+### Submitting a Pull Request
+
+Please follow these steps for all pull requests. These steps are derived from the [GitHub flow](https://help.github.com/articles/github-flow/).
+
+#### Step 1: Fork
+
+Fork the current repository and clone your fork
+locally.
+
+```sh
+git clone https://github.com/solacecommunity/<github-repo>
+```
+
+#### Step 2: Branch
+
+Make your changes on a new git branch in your fork of the repository.
+
+```sh
+git checkout -b my-fix-branch master
+```
+
+#### Step 3: Commit
+
+Commit your changes using a descriptive commit message.
+
+```sh
+git commit -a -m "Your Commit Message"
+```
+
+Note: the optional commit `-a` command line option will automatically "add" and "rm" edited files.
+
+#### Step 4: Rebase (if possible)
+
+Assuming you have not yet pushed your branch to origin, use `git rebase` (not `git merge`) to synchronize your work with the main
+repository.
+
+```sh
+$ git fetch upstream
+$ git rebase upstream/master
+```
+
+If you have not set the upstream, do so as follows:
+
+```sh
+$ git remote add upstream https://github.com/solacecommunity/<github-repo>
+```
+
+If you have already pushed your fork, then do not rebase. Instead merge any changes from master that are not already part of your branch.
+
+#### Step 5: Push
+
+Push your branch to your fork in GitHub:
+
+```sh
+git push origin my-fix-branch
+```
+
+#### Step 6: Pull Request
+
+In GitHub, send a pull request to `<github-repo>:master`.
+
+When fixing an existing issue, use the [commit message keywords](https://help.github.com/articles/closing-issues-via-commit-messages/) to close the associated GitHub issue.
+
+* If we suggest changes then:
+  * Make the required updates.
+  * Commit these changes to your branch (ex: my-fix-branch)
+
+That's it! Thank you for your contribution!
+
+## <a name="features"></a> **Do you have an ideas for a new feature or a change to an existing one?**
+
+* Open a GitHub issue and label it as an *enhancement* and describe the new functionality.
+
+##  <a name="questions"></a> Do you have questions about the source code?
+
+* Ask any question about the code or how to use Solace technologies in the [Solace community](https://solace.community).

LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2020 Solace Community
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

README.md

@@ -8,8 +8,8 @@ In order to be able to use the request/reply functionality, add the following se
 
 ```xml
 <dependency>
-    <groupId>ch.sbb.tms.platform</groupId>
-    <artifactId>spring-boot-starter-request-reply</artifactId>
+    <groupId>community.solace.spring.cloud</groupId>
+    <artifactId>spring-cloud-stream-starter-request-reply</artifactId>
 </dependency>
 ```