Hi again,

The issue was discovered during some work I was doing for Groovy-VFS. In that situtation the webdav provider is consumed and it will fail to work if anything JackRabbit 2.0+ is used as a depedency. The webdav provider released with VFS 2.0 is depending on a static field (BUILDER_FACTORY) in JackRabbit that no longer exists in the 2.0+ releases.

HTH

On 29/10/2015 07:37, Benedikt Ritter wrote:
Hi,

2015-10-29 2:17 GMT+01:00 <e...@zusammenkunft.net>:

Hello,

Unfortunatelly the whole webdav filesystem tests depend on that specific
version as it wraps the server as an endpoint. The setUp fails so the whole
test suite will get skipped. I havent been able to quickly fix when I tried
to bump the dependency (but it is not impossible, as you can also test
against other servers). But isnt this only a test dependency?

No, looks like it is an optional dependency in compile scope of vfs core [1]

Benedikt

[1]
https://github.com/apache/commons-vfs/blob/422c4f5d6822a77679a2c70166d72adb7d426c98/core/pom.xml#L83


Gruss
Bernd

--
http://bernd.eckenfels.net

-----Original Message-----
From: "Schalk Cronjé" <ysb...@gmail.com>
To: Commons Developers List <dev@commons.apache.org>
Sent: Do., 29 Okt. 2015 1:30 AM
Subject: [VFS] Jackrabbit

Bernd,

Is it possible to bump the Jackrabbit version to 2.11.1 for the VFS 2.1
release?

The current 1.6.5 is quite old and later versions of jackrabbit-webdav
cannot be used with the existing 2.0.

I did a quick check and there seems to be only one test failure when the
version is bumped:

     junit.framework.AssertionFailedError: Folder does not exist:
     webdav://admin@localhost:61279/repository/default/read-tests
          at junit.framework.Assert.fail(Assert.java:57)
          at junit.framework.Assert.assertTrue(Assert.java:22)
          at

org.apache.commons.vfs2.test.AbstractTestSuite.setUp(AbstractTestSuite.java:190)
          at

org.apache.commons.vfs2.provider.webdav.test.WebdavProviderTestCase$1.setUp(WebdavProviderTestCase.java:284)
          at

org.apache.commons.vfs2.test.AbstractTestSuite$1.protect(AbstractTestSuite.java:148)
          at junit.framework.TestResult.runProtected(TestResult.java:142)
          at

org.apache.commons.vfs2.test.AbstractTestSuite.run(AbstractTestSuite.java:154)
          at

org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:86)
          at

org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:283)
          at

org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:173)
          at

org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153)
          at

org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:128)
          at

org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:203)
          at

org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:155)
          at

org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103)


--
Schalk W. Cronjé
Twitter / Ello / Toeter : @ysb33r


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org




--
Schalk W. Cronjé
Twitter / Ello / Toeter : @ysb33r


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Reply via email to