So, It looks like upgrading the parent pom from #42 to #43 broke the build. This can be seen in the travis build history, and I have checked that mvn clean verify works with 42 and fails with 43.
On February 15, 2018 at 12:07:45, Otto Fowler (ottobackwa...@gmail.com) wrote: It is also failed on github On February 15, 2018 at 11:59:22, Otto Fowler (ottobackwa...@gmail.com) wrote: I have forked VFS and tried to build it in my personal travis, and it is failing. https://travis-ci.org/ottobackwards/commons-vfs/builds/341963824 It also fails testing locally as well. Is this expected? I can’t get the the apache/commons-vfs travis site to check if it is building there. ottO
