Bulletproof TFTPServerPathTest

[jkbkupczyk]

• Rewrite TFTPServerPathTest
• Add the TFTPServer::getPort method to return TFTPServer port

This PR tries to get rid of notoriously failing TFTPServerPathTest on Windows 8 on CI pipeline with the message TFTPServerPathTest.testReadOnly:82 Couldn't clear output location, deleted= ==> expected: <false> but was: <true>

FYI
@garydgregory @kinow

[kinow]

Code looks good, but there might be something else that needs to be done in the new test, CI failing on ubuntu + Java 8

Error:  Failures: 
Error:    TFTPServerPathTest.testWriteOnly:154 expected: <false> but was: <true>

Thank you!

[jkbkupczyk]

Code looks good, but there might be something else that needs to be done in the new test, CI failing on ubuntu + Java 8

Error:  Failures: 
Error:    TFTPServerPathTest.testWriteOnly:154 expected: <false> but was: <true>

Thank you!

Thank you @kinow for the fast response!
I removed the logic of verifying the written contents and moved it to another test TFTPServerPathTest::testWriteVerifyContents. I think it should work RN :)

[garydgregory]

@jkbkupczyk
Would you please rebase on master?

[jkbkupczyk]

@jkbkupczyk Would you please rebase on master?

done

[garydgregory]

TY @jkbkupczyk !

[jkbkupczyk]

Thank you @garydgregory and @kinow for review!

[garydgregory]

@jkbkupczyk
Still fails : https://github.com/apache/commons-net/actions/runs/6213336399/job/16864291327

[jkbkupczyk]

@jkbkupczyk Still fails : https://github.com/apache/commons-net/actions/runs/6213336399/job/16864291327

Hm, I think it's because files have the same name, I will create a patch that will address this issue.

[garydgregory]

@jkbkupczyk Still fails : https://github.com/apache/commons-net/actions/runs/6213336399/job/16864291327

Hm, I think it's because files have the same name, I will create a patch that will address this issue.

TY!

[jkbkupczyk]

@jkbkupczyk Still fails : https://github.com/apache/commons-net/actions/runs/6213336399/job/16864291327

Hm, I think it's because files have the same name, I will create a patch that will address this issue.

TY!

I created patch #184