You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Update Cloudsoft's Winrm Library Dependencies from Javax to Jakarta for Spring Boot 3 Compatibility #171
We are in the process of migrating our application to Spring Boot 3. During this migration, we encountered an issue with Cloudsoft's winrm library, which is currently using Javax dependencies. Spring Boot 3 requires Jakarta dependencies instead of Javax.
Migrating to Jakarta EE is a critical step in leveraging the new features and improvements offered by Spring Boot 3. Ensuring compatibility with Jakarta dependencies will help in maintaining the robustness and future scalability of the application.
We appreciate your prompt attention to this issue and look forward to your guidance on resolving it.
If you're looking for an actively maintained alternative to winrm4j, we maintain winrm-java, another WinRM (light) client for Java and its documentation with zero runtime dependencies, designed to be easy to migrate to from winrm4j:
winrm4j 0.12.x
winrm-java 2.1
Dependencies
Apache CXF + HttpClient + JAXB (dozens of jars)
None (single ~300 kB jar)
Java
8 (needs manual JAX-WS/JAXB additions on 11+)
11+ (works out of the box on current JDKs)
Commands & PowerShell
executeCommand / executePs
command(...) / powerShell(...) — no script size limit, no escaping
There's a dedicated migration guide mapping every WinRmTool / WinRmClientBuilder option to its equivalent, including the behavioral differences to watch for
Maven coordinates: org.metricshub:winrm-java:2.1.00, and license is Apache-2.0, like winrm4j.
Activity
bertysentry commentedon Aug 11, 2026
Hi! 👋
If you're looking for an actively maintained alternative to winrm4j, we maintain winrm-java, another WinRM (light) client for Java and its documentation with zero runtime dependencies, designed to be easy to migrate to from winrm4j:
executeCommand/executePscommand(...)/powerShell(...)— no script size limit, no escapingProcess-style streamingMigration is pretty straightforward:
There's a dedicated migration guide mapping every
WinRmTool/WinRmClientBuilderoption to its equivalent, including the behavioral differences to watch forMaven coordinates:
org.metricshub:winrm-java:2.1.00, and license is Apache-2.0, like winrm4j.