Standards & Tooling: Implement Gradle & Use Conventional Source Paths

[TheFlagCourier]

This PR addresses three primary things:

• Applies resource filtering (Both Maven & Gradle) [Prior oversight?]
• Uses standardized source and resources paths
• Implements the Gradle build system (Gradle 9.0.0)

Standardized Source & Resource Paths

• src/net/ > src/main/java/net/
• create src/main/resources/
• move plugin.yml to src/main/resources/
• copy license.txt to resource directory (not written to plugins directory, yet; still contained in the JAR)
• Update Maven's pom to point to new directories and include the license.

Gradle Implementation

• Based on the implementation effort found in VaultUnlockedAPI
• Uses Shadow to shade & relocate bstats; and apply manifest attributes.
• Publication will publish the ShadowJar (Mimics Maven)
• Jar task will build the unshaded jar with -original qualifier suffix.

[CLAassistant]

All committers have signed the CLA.

[creatorfromhell]

This PR addresses three primary things:

• Applies resource filtering (Both Maven & Gradle) [Prior oversight?]
• Uses standardized source and resources paths
• Implements the Gradle build system (Gradle 9.0.0)

Standardized Source & Resource Paths

• src/net/ > src/main/java/net/
• create src/main/resources/
• move plugin.yml to src/main/resources/
• copy license.txt to resource directory (not written to plugins directory, yet; still contained in the JAR)
• Update Maven's pom to point to new directories and include the license.

Gradle Implementation

• Based on the implementation effort found in VaultUnlockedAPI
• Uses Shadow to shade & relocate bstats; and apply manifest attributes.
• Publication will publish the ShadowJar (Mimics Maven)
• Jar task will build the unshaded jar with -original qualifier suffix.

Just noticed this one is complete now, is it working properly?

[TheFlagCourier]

@creatorfromhell Should be good to go, if you're happy with how it builds. The main point of contention would be the changing of the source directory path - which may require other branches / forks / prs to be rebased.

[creatorfromhell]

@creatorfromhell Should be good to go, if you're happy with how it builds. The main point of contention would be the changing of the source directory path - which may require other branches / forks / prs to be rebased.

That sounds good with me. Cheers.