woonsan commented on issue #52: VFS-686: webdav4 provider based on the latest
Jackrabbit 2.x
URL: https://github.com/apache/commons-vfs/pull/52#issuecomment-543232040
@garydgregory , after confirming local build with oracle-jdk11 working fine,
I kicked in travis again and it seems to build
woonsan commented on issue #52: VFS-686: webdav4 provider based on the latest
Jackrabbit 2.x
URL: https://github.com/apache/commons-vfs/pull/52#issuecomment-497156049
On second thought, it seems better to rename "commons-vfs2-jackrabbit2" to
"commons-vfs2-jackrabbit", and "commons-vfs2-jac
woonsan commented on issue #52: VFS-686: webdav4 provider based on the latest
Jackrabbit 2.x
URL: https://github.com/apache/commons-vfs/pull/52#issuecomment-488129264
Hi @garydgregory ,
I don't know, but the patch file downloaded from GitHub seems to make
problems.
I found an alterna
woonsan commented on issue #52: VFS-686: webdav4 provider based on the latest
Jackrabbit 2.x
URL: https://github.com/apache/commons-vfs/pull/52#issuecomment-487989859
Hi @garydgregory ,
I've just merged mater. It's great to see greens even for JVM11! Great work!
Woonsan
-
woonsan commented on issue #52: VFS-686: webdav4 provider based on the latest
Jackrabbit 2.x
URL: https://github.com/apache/commons-vfs/pull/52#issuecomment-483062377
BTW, I'm open to any better name suggestions. On top off my head,
"commons-vfs2-jackrabbit2-hc3" (with updating the version
woonsan commented on issue #52: VFS-686: webdav4 provider based on the latest
Jackrabbit 2.x
URL: https://github.com/apache/commons-vfs/pull/52#issuecomment-483057288
Hi @garydgregory ,
Yes, the naming is tricky here. The main reason I mentioned is that
Jackrabbit2 had upgraded its
woonsan commented on issue #52: VFS-686: webdav4 provider based on the latest
Jackrabbit 2.x
URL: https://github.com/apache/commons-vfs/pull/52#issuecomment-482395737
Now it's really ready to review. It now depends on the latest JR release:
2.19.2. Thanks!
woonsan commented on issue #52: VFS-686: webdav4 provider based on the latest
Jackrabbit 2.x
URL: https://github.com/apache/commons-vfs/pull/52#issuecomment-479550829
Hi @garydgregory ,
This PR is now ready to review!
This PR includes (a) new `webdav4` provider based on the la
woonsan commented on issue #52: VFS-686: webdav4 provider based on the latest
Jackrabbit 2.x
URL: https://github.com/apache/commons-vfs/pull/52#issuecomment-479304944
Hi @garydgregory ,
Yet not ready status because jackrabbit3 submodule depends on the following
(in root pom):
> 2.19.
woonsan commented on issue #52: VFS-686: webdav4 provider based on the latest
Jackrabbit 2.x
URL: https://github.com/apache/commons-vfs/pull/52#issuecomment-479279513
Hi @garydgregory , I think I found the cause. It's all my bad. For some
reason -- probably due to my git env setting, some
woonsan commented on issue #52: VFS-686: webdav4 provider based on the latest
Jackrabbit 2.x
URL: https://github.com/apache/commons-vfs/pull/52#issuecomment-479276504
@garydgregory , just fyi, I'm trying to figure out how to reproduce this
locally. Strangely, my local tests were successful
woonsan commented on issue #52: VFS-686: webdav4 provider based on the latest
Jackrabbit 2.x
URL: https://github.com/apache/commons-vfs/pull/52#issuecomment-478699483
@garydgregory , when I merged master locally, it started failing like that...
Some test env setting might have changed
b
woonsan commented on issue #52: VFS-686: webdav4 provider based on the latest
Jackrabbit 2.x
URL: https://github.com/apache/commons-vfs/pull/52#issuecomment-478629869
> I see a merge from trunk but that branch should not exist. Please master.
Thank you so much @garydgregory ! I've ju
13 matches
Mail list logo
