From bbcc357f33d542f095948d55f1dfd7fc0c128f48 Mon Sep 17 00:00:00 2001
From: Snabeldier <79211348+Snabeldier@users.noreply.github.com>
Date: Mon, 6 Jan 2025 20:39:38 +0100
Subject: [PATCH] take use of list elements
---
README.md | 82 +++++++++++++++++++++++++++++++------------------------
1 file changed, 47 insertions(+), 35 deletions(-)
diff --git a/README.md b/README.md
index 9b88ae8..a6cdd10 100644
--- a/README.md
+++ b/README.md
@@ -3,7 +3,8 @@
The CoreAPI provides essential features and access to the internal server core of MineValleyEU, used in all modules.
> [!NOTE]\
-> The documentation for this API is still a work in progress and does not yet cover the entire functionality. We are working on adding more Javadoc to make the API easier to use.
+> The documentation for this API is still a work in progress and does not yet cover the entire functionality. We are
+> working on adding more Javadoc to make the API easier to use.
## Maven Integration
@@ -11,31 +12,36 @@ To use the CoreAPI in your module, we provide a Maven repository hosted on GitHu
Before proceeding, ensure you’ve added a token to your `settings.xml` file (details below).
```xml
+
- github
- https://maven.pkg.github.com/MineValley/CoreAPI
-
- true
-
+ github
+ https://maven.pkg.github.com/MineValley/CoreAPI
+
+ true
+
```
```xml
+
- minevalley.core
- api
- LATEST
+ minevalley.core
+ api
+ LATEST
```
## Linking Your GitHub Account
-While the API is publicly accessible, a GitHub account is required to access the repository. If you already have an account, follow these steps to create a token:
+While the API is publicly accessible, a GitHub account is required to access the repository. If you already have an
+account, follow these steps to create a token:
> [!IMPORTANT]\
-> Opting for a token with no expiration increases the likelihood of unauthorized access and should be carefully considered.\
-> Reusing the same token across multiple purposes or devices significantly increases the potential damage in the event of a leak.
+> Opting for a token with no expiration increases the likelihood of unauthorized access and should be carefully
+> considered.\
+> Reusing the same token across multiple purposes or devices significantly increases the potential damage in the event
+> of a leak.
### Creating a Personal Access Token
@@ -50,45 +56,51 @@ While the API is publicly accessible, a GitHub account is required to access the
### Adding the Token to Your Maven Settings
-Once you have your token, add it to the `settings.xml` file of your Maven installation. Replace `USERNAME` with your GitHub username and `TOKEN` with the generated token.
+Once you have your token, add it to the `settings.xml` file of your Maven installation. Replace `USERNAME` with your
+GitHub username and `TOKEN` with the generated token.
+
```xml
-
-
- github
- USERNAME
- TOKEN
-
-
+
+
+ github
+ USERNAME
+ TOKEN
+
+
```
-> **Tip**: In IntelliJ, you can create a `settings.xml` file by right-clicking on the `pom.xml` of any project and selecting **Create settings.xml**.
-## Troubleshooting / FAQ
+> **Tip**: In IntelliJ, you can create a `settings.xml` file by right-clicking on the `pom.xml` of any project and
+> selecting **Create settings.xml**.
+## Troubleshooting / FAQ
I'm having issues with Eclipse.
-
-Use IntelliJ.
+
I’m unsure if I used the correct GitHub username.
-
-You can find your GitHub username on your profile page. If in doubt, try logging in with your username. If it works, it’s correct.
+
+ - You can find your GitHub username on your profile page. If in doubt, try logging in with your username. If it works,
+it’s correct.
+
Can I choose the content of <id> freely?
-
-Yes, the content of `` in both the `settings.xml` and `pom.xml` files can be freely chosen, but it must be identical in both files.
+
+ - Yes, the content of `` in both the `settings.xml` and `pom.xml` files can be freely chosen, but it must be identical
+in both files.
+
I followed all steps, but the dependency could not be found.
-
-1. Click **Maven** in the right-hand sidebar.
-
-2. Press the **Reload All Maven Projects** button (top-left).
-
-3. If the problem persists, go to **File** → **Invalidate Caches ...** → **Invalidate and Restart**.
-
+
+ - Click **Maven** in the right-hand sidebar.
+ - Press the **Reload All Maven Projects** button (top-left).
+ - If the problem persists, go to **File** → **Invalidate Caches ...** → **Invalidate and Restart**.
+
\ No newline at end of file