Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

VFS-783: Proper http scheme setting on webdav/webdav2 with unit tests #143

Merged
merged 5 commits into from
Dec 10, 2020
Merged

VFS-783: Proper http scheme setting on webdav/webdav2 with unit tests #143

merged 5 commits into from
Dec 10, 2020

Conversation

woonsan
Copy link
Contributor

@woonsan woonsan commented Oct 19, 2020

This is just to add unit tests for the @satish-csi 's pull request: #118.
I have cherry-picked @satish-csi 's commits in the feature branch and added a unit test class for the fix.
Please review and merge it if okay. Thanks!

asfgit pushed a commit that referenced this pull request Oct 31, 2020
#143.

As of git master today, #143
does not prove anything has been fixed:
- Add  ONLY
`org.apache.commons.vfs2.provider.webdav4.Webdav4FileObject.getInternalURI()`
- Add `Webdav4FileObjectTest`. run it, and it passes.
Therefore, I've only committed these changes but with changes to
`Webdav4FileObjectTest` to add try-with-resources blocks.
@garydgregory
Copy link
Member

garydgregory commented Oct 31, 2020

Hi @woonsan
As of git master today, this test does not prove anything has been fixed:

  • Add ONLY org.apache.commons.vfs2.provider.webdav4.Webdav4FileObject.getInternalURI()
  • Add Webdav4FileObjectTest, run it, and it passes.
    Therefore, I've only committed these changes but with changes to Webdav4FileObjectTest to add try-with-resources blocks.

May you please update to git master and see if you can update the test or provide a new one?

@woonsan
Copy link
Contributor Author

woonsan commented Oct 31, 2020

Hi @garydgregory ,
Thank you so much for the pointers! I should have verified it properly, sorry for that.
I've pushed a new commit after checking the failure by the test and fix. Would you please take a look?
Cheers,
Woonsan

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.

3 participants