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.

Sign up for GitHub

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

Jump to bottom

hypersistence-utils/hypersistence-utils-parent-3.5.1 build #5795

Closed
dplavcic opened this issue Aug 10, 2023 · 3 comments
Closed

hypersistence-utils/hypersistence-utils-parent-3.5.1 build #5795

dplavcic opened this issue Aug 10, 2023 · 3 comments
Labels
stale

Comments

@dplavcic
Copy link

Please provide:

Thank you!
@github-actions
Copy link

This issue is stale because it has been open for 30 days with no activity.

@github-actions github-actions bot added the stale label Sep 10, 2023
@github-actions
Copy link

This issue was closed because it has been inactive for 14 days since being marked as stale.

@dplavcic
Copy link
Author

dplavcic commented Nov 3, 2023

Bump. Not fixed...

Stephan202 added a commit to PicnicSupermarket/error-prone that referenced this issue Aug 31, 2024
@Stephan202
Ensure Jitpack compatibility
9061447 
By default Jitpack builds with Java 11.0.2 and Maven 3.6.1.
Additionally, its read-only `/script/toolchains.xml` file points to at
least one nonexistent JDK home directory. See jitpack/jitpack.io#5795.

These days Error Prone releases are built using JDK 17 and require at
least Maven 3.6.3. Additionally, its `maven-toolchains-plugin`
configuration rejects invalid `toolchains.xml` configurations.

As such this change uses SDKMAN! to configure recent Java and Maven
versions, and modifies the build by disabling Maven Toolchains usage.
@Stephan202 Stephan202 mentioned this issue Aug 31, 2024
Merged
1 task
Stephan202 added a commit to PicnicSupermarket/error-prone that referenced this issue Sep 11, 2024
@Stephan202
Ensure Jitpack compatibility
6b9b1d2 
By default Jitpack builds with Java 11.0.2 and Maven 3.6.1.
Additionally, its read-only `/script/toolchains.xml` file points to at
least one nonexistent JDK home directory. See jitpack/jitpack.io#5795.

These days Error Prone releases are built using JDK 17 and require at
least Maven 3.6.3. Additionally, its `maven-toolchains-plugin`
configuration rejects invalid `toolchains.xml` configurations.

As such this change uses SDKMAN! to configure recent Java and Maven
versions, and modifies the build by disabling Maven Toolchains usage.
Stephan202 added a commit to PicnicSupermarket/error-prone that referenced this issue Oct 1, 2024
@Stephan202
Ensure Jitpack compatibility
6bb9195 
By default Jitpack builds with Java 11.0.2 and Maven 3.6.1.
Additionally, its read-only `/script/toolchains.xml` file points to at
least one nonexistent JDK home directory. See jitpack/jitpack.io#5795.

These days Error Prone releases are built using JDK 17 and require at
least Maven 3.6.3. Additionally, its `maven-toolchains-plugin`
configuration rejects invalid `toolchains.xml` configurations.

As such this change uses SDKMAN! to configure recent Java and Maven
versions, and modifies the build by disabling Maven Toolchains usage.
Stephan202 added a commit to PicnicSupermarket/error-prone that referenced this issue Oct 19, 2024
@Stephan202
Ensure Jitpack compatibility
5e2a82c 
By default Jitpack builds with Java 11.0.2 and Maven 3.6.1.
Additionally, its read-only `/script/toolchains.xml` file points to at
least one nonexistent JDK home directory. See jitpack/jitpack.io#5795.

These days Error Prone releases are built using JDK 17 and require at
least Maven 3.6.3. Additionally, its `maven-toolchains-plugin`
configuration rejects invalid `toolchains.xml` configurations.

As such this change uses SDKMAN! to configure recent Java and Maven
versions, and modifies the build by disabling Maven Toolchains usage.
Stephan202 added a commit to PicnicSupermarket/error-prone that referenced this issue Oct 26, 2024
@Stephan202
Ensure Jitpack compatibility
a4e3306 
By default Jitpack builds with Java 11.0.2 and Maven 3.6.1.
Additionally, its read-only `/script/toolchains.xml` file points to at
least one nonexistent JDK home directory. See jitpack/jitpack.io#5795.

These days Error Prone releases are built using JDK 17 and require at
least Maven 3.6.3. Additionally, its `maven-toolchains-plugin`
configuration rejects invalid `toolchains.xml` configurations.

As such this change uses SDKMAN! to configure recent Java and Maven
versions, and modifies the build by disabling Maven Toolchains usage.
Stephan202 added a commit to PicnicSupermarket/error-prone that referenced this issue Oct 26, 2024
@Stephan202
Ensure Jitpack compatibility
18f8391 
By default Jitpack builds with Java 11.0.2 and Maven 3.6.1.
Additionally, its read-only `/script/toolchains.xml` file points to at
least one nonexistent JDK home directory. See jitpack/jitpack.io#5795.

These days Error Prone releases are built using JDK 17 and require at
least Maven 3.6.3. Additionally, its `maven-toolchains-plugin`
configuration rejects invalid `toolchains.xml` configurations.

As such this change uses SDKMAN! to configure recent Java and Maven
versions, and modifies the build by disabling Maven Toolchains usage.
Stephan202 added a commit to PicnicSupermarket/error-prone that referenced this issue Nov 19, 2024
@Stephan202
Ensure Jitpack compatibility
f1cbe01 
By default Jitpack builds with Java 11.0.2 and Maven 3.6.1.
Additionally, its read-only `/script/toolchains.xml` file points to at
least one nonexistent JDK home directory. See jitpack/jitpack.io#5795.

These days Error Prone releases are built using JDK 17 and require at
least Maven 3.6.3. Additionally, its `maven-toolchains-plugin`
configuration rejects invalid `toolchains.xml` configurations.

As such this change uses SDKMAN! to configure recent Java and Maven
versions, and modifies the build by disabling Maven Toolchains usage.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
stale
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@dplavcic