Skip to content

Move to Java17 #438

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

Closed
wants to merge 1 commit into from
Closed

Move to Java17 #438

wants to merge 1 commit into from

Conversation

cstamas
Copy link
Member

@cstamas cstamas commented Mar 10, 2024

Changes:

  • update to Maven 4 alpha-13 (is Java 17)
  • lift release=17 (was 8 but build requirement was 21)
  • collapse JDK transport (no need for 8 and 11 modules anymore, baseline is 17)
  • add modernizer to prevent legacy code

@cstamas cstamas self-assigned this Mar 10, 2024
import org.eclipse.aether.spi.connector.transport.PeekTask;
import org.eclipse.aether.spi.connector.transport.PutTask;
import org.eclipse.aether.spi.connector.transport.TransportTask;
import org.eclipse.aether.spi.connector.transport.*;
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

😄

Copy link
Member

@michael-o michael-o left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Isn't it enough to have one JDK module since there is one new HttpClient there?

<name>Maven Artifact Resolver Transport JDK 11</name>
<description>Maven Artifact Transport JDK Java 11+.</description>
<name>Maven Artifact Resolver Transport JDK 17</name>
<description>Maven Artifact Transport JDK Java 17+.</description>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why? Can't it then just be "Maven Artifact Resolver Transport JDK" or so?

| 92. | `"aether.transport.jdk.httpVersion"` | `java.lang.String` | Use string representation of HttpClient version enum "HTTP_2" or "HTTP_1_1" to set default HTTP protocol to use. | `"HTTP_2"` | 2.0.0 | Yes | Session Configuration |
| 93. | `"aether.transport.jdk.maxConcurrentRequests"` | `java.lang.Integer` | The hard limit of maximum concurrent requests JDK transport can do. This is a workaround for the fact, that in HTTP/2 mode, JDK HttpClient initializes this value to Integer.MAX_VALUE (!) and lowers it on first response from the remote server (but it may be too late). See JDK bug <a href="https://bugs.openjdk.org/browse/JDK-8225647">JDK-8225647</a> for details. | `100` | 2.0.0 | Yes | Session Configuration |
| 92. | `"aether.transport.jdk.httpVersion"` | `String` | Use string representation of HttpClient version enum "HTTP_2" or "HTTP_1_1" to set default HTTP protocol to use. | `"HTTP_2"` | 2.0.0 | Yes | Session Configuration |
| 93. | `"aether.transport.jdk.maxConcurrentRequests"` | `Integer` | The hard limit of maximum concurrent requests JDK transport can do. This is a workaround for the fact, that in HTTP/2 mode, JDK HttpClient initializes this value to Integer.MAX_VALUE (!) and lowers it on first response from the remote server (but it may be too late). See JDK bug <a href="https://bugs.openjdk.org/browse/JDK-8225647">JDK-8225647</a> for details. | `100` | 2.0.0 | Yes | Session Configuration |
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This does not make sense if the other references are still fully qualified and I would leave it fully qualified for consistency.

@michael-o
Copy link
Member

A JIRA issue is also advised.

@elharo
Copy link
Contributor

elharo commented Feb 16, 2025

I think this is obdolete since project is now on java 21?

@elharo elharo added the waiting-for-feedback Waiting for 90 days until issues or pull request will be closed label Feb 16, 2025
@michael-o
Copy link
Member

I think this is obdolete since project is now on java 21?

This is runtime requirement, not build time

Copy link

This pull request is stale because it has been waiting for feedback for 60 days. Remove the stale label or comment on this PR, or it will be automatically closed in 30 days.

@github-actions github-actions bot added the Stale label Apr 26, 2025
@slachiewicz
Copy link
Member

slachiewicz commented May 13, 2025

@cstamas Maybe worth cleaning up artefacts before Maven4?

@github-actions github-actions bot removed waiting-for-feedback Waiting for 90 days until issues or pull request will be closed Stale labels May 13, 2025
@cstamas
Copy link
Member Author

cstamas commented May 13, 2025

Will happen in resolver 2.1

@cstamas cstamas closed this May 13, 2025
@michael-o
Copy link
Member

Will happen in resolver 2.1

Shouldn't this happen with 3.0 and a namespace change for Maven 4/5?

@cstamas
Copy link
Member Author

cstamas commented May 13, 2025

Or that, yes: point in point: not in 2.0.x

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants