Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make jitpack build using java 16 #5309

Merged
merged 1 commit into from
Sep 25, 2021
Merged

Make jitpack build using java 16 #5309

merged 1 commit into from
Sep 25, 2021

Conversation

Warriorrrr
Copy link
Member

Description:


New Nodes/Commands/ConfigOptions:


Relevant Towny Issue ticket:


  • I have tested this pull request for defects on a server.

By making this pull request, I represent that I have the right to waive copyright and related rights to my contribution, and agree that all copyright and related rights in my contributions are waived, and I acknowledge that the TownyAdvanced organization has the copyright to use and modify my contribution under the Towny License for perpetuity.

@Warriorrrr Warriorrrr added the bug label Sep 25, 2021
@Warriorrrr Warriorrrr added this to the 0.97.2.0 milestone Sep 25, 2021
@LlmDl LlmDl merged commit 4c9430f into master Sep 25, 2021
@LlmDl LlmDl deleted the fix/jitpack-building branch September 25, 2021 14:46
TheFlagCourier added a commit that referenced this pull request Oct 20, 2021
This commit supplants changes made in #5309 and the following direct commits:
- 547c631
- d5362ba

This re-write of the `jitpack.yml` file removes the direct jdk declaration and 3rd-party fallback script (`https://github.com/sormuras/bach/raw/master/install-jdk.sh`) in favor of utilizing the _SDKMAN!_ package manager included in Jitpack's VMs.

It provides the following, without the need of a 3rd-party script:
- Specification of the JDK version and distribution. (Jitpack defaults to OpenJDK 8)
- Specification of the version of Apache Maven. (Jitpack defaults to 3.6.x at time of commit)

The following considerations were made:
- Use the latest available LTS JDK (Java 17)
- Use the Microsoft OpenJDK builds, as it is the common vendor for Minecraft's distribution, and would therefore likely continue to include
- Use the latest compatible Maven tooling (Maven 3.8.3, )
LlmDl pushed a commit that referenced this pull request Oct 20, 2021
…Pack configuration (#5386)

* Force JitPack to use SDKMAN!; use Java 17 and Maven 3.8.3
This commit supplants changes made in #5309 and the following direct commits:
- 547c631
- d5362ba

This re-write of the `jitpack.yml` file removes the direct jdk declaration and 3rd-party fallback script (`https://github.com/sormuras/bach/raw/master/install-jdk.sh`) in favor of utilizing the _SDKMAN!_ package manager included in Jitpack's VMs.

It provides the following, without the need of a 3rd-party script:
- Specification of the JDK version and distribution. (Jitpack defaults to OpenJDK 8)
- Specification of the version of Apache Maven. (Jitpack defaults to 3.6.x at time of commit)

The following considerations were made:
- Use the latest available LTS JDK (Java 17)
- Use the Microsoft OpenJDK builds, as it is the common vendor for Minecraft's distribution, and would therefore likely continue to include
- Use the latest compatible Maven tooling (Maven 3.8.3, )

* Update Dependencies
- HikariCP 4.0.3 >> 5.0.0 [changes](brettwooldridge/HikariCP@HikariCP-4.0.3...HikariCP-5.0.0)
- JetBrains Annotations 21.0.1 >> 22.0.0 (Adds `@Blocking` and `@NonBlocking`)
- Adventure Platform, Bukkit 4.0.0-SNAPSHOT >> 4.0.0 (Finalized Version)
- Maven Javadoc Plugin 3.2.0 >> 3.3.1 [changes](apache/maven-javadoc-plugin@maven-javadoc-plugin-3.2.0...maven-javadoc-plugin-3.3.1)

* Update GitHub Actions
- Use Eclipse Temurin 17 as OpenJDK provider (Replacing the legacy AdoptOpenJDK version)
- Have compile-on-push.yml test against _both_ Java 16 and Java 17.
- Use Java 17 for deployment builds.

* Remove 'Overlapping Class' warning for Kyori's ExaminationAPI
Both Examination-API and Examination-String contain a file at `META-INF/versions/9/module-info.class`

Since we are not a modular project, and we do not directly depend on these, it's safe to filter these out of the build to prevent collisions.

* JitPack: Use Temurin instead of MS-OpenJDK
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants