Skip to content

Conversation

@cstamas
Copy link
Member

@cstamas cstamas commented Sep 18, 2025

This change was done due Windows, but later the execution path was split for Windows to use oldie pre-NIO2 code to copy as for some reason that works on Windows.

On other platforms, insist on ATOMIC, still make use able to override it, in case atomic is not a viable option.

This change was done due Windows, but later the execution
path was split for Windows to use oldie pre-NIO2 code to
copy as for some reason that works on Windows.

On other platforms, insist on ATOMIC.
@cstamas cstamas self-assigned this Sep 18, 2025
@cstamas cstamas marked this pull request as ready for review September 18, 2025 22:12
@cstamas cstamas added this to the 2.0.12 milestone Sep 18, 2025
@cstamas
Copy link
Member Author

cstamas commented Sep 18, 2025

make it configurable...

To provide at least some "escape hatch" for those not being
able to use atomic moves.
@cstamas cstamas merged commit ebe4ae4 into apache:master Sep 19, 2025
8 checks passed
@cstamas cstamas deleted the go-back-to-atomic branch September 19, 2025 09:41
@github-actions
Copy link

@cstamas Please assign appropriate label to PR according to the type of change.

cstamas added a commit to cstamas/maven-resolver that referenced this pull request Sep 19, 2025
This change was done due Windows, but later the execution path was split for Windows to use oldie pre-NIO2 code to copy as for some reason that works on Windows.

On other platforms, insist on ATOMIC, still make use able to override it, in case atomic is not a viable option.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant