[Tests] FTP: Use restrictions to bypass cert setup issues #6415
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently both
FtpTestResource
andFtpsTestResource
are instantiated before the first test runs.The current method did not work when executing only the native tests (
-Pnative -Dtest="\!*" -Dsurefire.failIfNoSpecifiedTests=false
) without jvm tests. When running with-Pnative
only (so jvm tests first, then native), the problem did not occur, as theFtpsIT
did not actually use the certificates defined inFtpsTest
, but reused the certificates generated by the invocation ofSftpTest
in jvm mode.When running with
-Pnative -Dtest="\!*" -Dsurefire.failIfNoSpecifiedTests=false
, the "workflow" without this change was:With this change, the order is:
please also backport to 3.8 when merged