Skip to content

Use main branch of HTTP client#185

Merged
tadamski merged 1 commit intowildfly:mainfrom
marekkopecky:mainBranchForHttpClient
Oct 20, 2025
Merged

Use main branch of HTTP client#185
tadamski merged 1 commit intowildfly:mainfrom
marekkopecky:mainBranchForHttpClient

Conversation

@marekkopecky
Copy link
Contributor

@marekkopecky marekkopecky commented Sep 11, 2025

Wildfly is not using 2.0 branch any more, so we should use latest branch again.

https://github.com/wildfly/wildfly/blob/main/pom.xml#L539

See also related discussions here: https://issues.redhat.com/browse/JBEAP-29502#

See this link for launcher changes: https://issues.redhat.com/browse/WFCORE-7044

@marekkopecky marekkopecky force-pushed the mainBranchForHttpClient branch 3 times, most recently from f9ff4fc to 4d22c4e Compare September 11, 2025 12:49
@marekkopecky
Copy link
Contributor Author

Original change is ok, but it seems that the upstream CI is broken for a long time, let me investigate this as a part of this PR ....

@marekkopecky marekkopecky force-pushed the mainBranchForHttpClient branch from 4d22c4e to 2216efc Compare October 10, 2025 10:24
@marekkopecky marekkopecky force-pushed the mainBranchForHttpClient branch 2 times, most recently from bf12b45 to 0a4d38d Compare October 20, 2025 11:49
<groupId>org.wildfly.launcher</groupId>
<artifactId>wildfly-launcher</artifactId>
<version>${version.wf.core}</version>
<version>1.0.2.Final</version>
Copy link
Contributor

Choose a reason for hiding this comment

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

hmm maybe we can move it to version properties as well just to keep it consistent?

@marekkopecky marekkopecky force-pushed the mainBranchForHttpClient branch from 0a4d38d to bb33d6c Compare October 20, 2025 13:13
@tadamski tadamski merged commit 893e559 into wildfly:main Oct 20, 2025
1 check passed
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.

2 participants