|
| 1 | +# Contribute to the STACKIT Java SDK |
| 2 | + |
| 3 | +Your contribution is welcome! Thank you for your interest in contributing to the STACKIT Java SDK. |
| 4 | +We greatly value your feedback, feature requests, additions to the code, bug reports or documentation extensions. |
| 5 | + |
| 6 | +## Table of contents |
| 7 | + |
| 8 | +- [Developer Guide](#developer-guide) |
| 9 | + - [Repository structure](#repository-structure) |
| 10 | +- [Code Contributions](#code-contributions) |
| 11 | +- [Bug Reports](#bug-reports) |
| 12 | + |
| 13 | +## Developer Guide |
| 14 | + |
| 15 | +Building the STACKIT Java SDK requires: |
| 16 | +1. Java SDK (version 11 to 21 should be supported) installed on your system |
| 17 | + |
| 18 | +In case you want to open the project in your preferred IDE, run `./gradlew idea` or `./gradlew eclipse` beforehand. |
| 19 | + |
| 20 | +#### Useful Make commands |
| 21 | + |
| 22 | +These commands can be executed from the project root: |
| 23 | + |
| 24 | +- `make fmt` or `./gradlew spotlessApply`: apply code format. |
| 25 | +- `make test` or `./gradlew test`: run unit tests. |
| 26 | + |
| 27 | +#### Installation |
| 28 | + |
| 29 | +To install the API client library to your local Maven repository, simply execute: |
| 30 | + |
| 31 | +```bash |
| 32 | +./gradlew publishToMavenLocal |
| 33 | +``` |
| 34 | + |
| 35 | +### Repository structure |
| 36 | + |
| 37 | +The STACKIT Java SDK service submodules are located under `services`. |
| 38 | +The files located in `services/[service]` are automatically generated from the [REST API specs](https://github.com/stackitcloud/stackit-api-specifications), whereas the ones located in subfolders (like `wait`) are manually maintained. Therefore, changes to files located in `services/[service]` will not be accepted. Instead, consider proposing changes to the generation process in the [Generator repository](https://github.com/stackitcloud/stackit-sdk-generator). |
| 39 | + |
| 40 | +Inside the `core` submodule you can find several classes that are used by all service modules. Examples of usage of the SDK are located in the `examples` directory. |
| 41 | + |
| 42 | +## Code Contributions |
| 43 | + |
| 44 | +To make your contribution, follow these steps: |
| 45 | + |
| 46 | +1. Check open or recently closed [Pull Requests](https://github.com/stackitcloud/stackit-sdk-java/pulls) and [Issues](https://github.com/stackitcloud/stackit-sdk-java/issues) to make sure the contribution you are making has not been already tackled by someone else. |
| 47 | +2. Fork the repo. |
| 48 | +3. Make your changes in a branch that is up-to-date with the original repo's `main` branch. |
| 49 | +4. Commit your changes including a descriptive message. |
| 50 | +5. Create a pull request with your changes. |
| 51 | +6. The pull request will be reviewed by the repo maintainers. If you need to make further changes, make additional commits to keep commit history. When the PR is merged, commits will be squashed. |
| 52 | + |
| 53 | +## Bug Reports |
| 54 | + |
| 55 | +If you would like to report a bug, please open a [GitHub issue](https://github.com/stackitcloud/stackit-sdk-java/issues/new). |
| 56 | + |
| 57 | +To ensure we can provide the best support to your issue, follow these guidelines: |
| 58 | + |
| 59 | +1. Go through the existing issues to check if your issue has already been reported. |
| 60 | +2. Make sure you are using the latest version of the SDK modules, we will not provide bug fixes for older versions. Also, latest versions may have the fix for your bug. |
| 61 | +3. Please provide as much information as you can about your environment, e.g. your version of Java, your version of the SDK modules, which operating system you are using and the corresponding version. |
| 62 | +4. Include in your issue the steps to reproduce it, along with code snippets and/or information about your specific use case. This will make the support process much easier and efficient. |
| 63 | + |
0 commit comments