On 24.1.13 12:10, Jukka Zitting wrote:
Hi,

On Thu, Jan 24, 2013 at 1:09 PM, Michael Dürig <[email protected]> wrote:
This is caused by the latest jcr-tests snapshot, which includes the fix for
JCR-3499 not being available to the buildbot. Isn't running the Jenkins
build for Jackrabbit enough to deploy these artefacts?

I suspect that either the Jackrabbit CI build didn't yet deploy fresh
snapshots, or the Oak build still had older Jackrabbit snapshots
cached locally. The issue should resolve itself soon.

mvn -U would probably do the job.

Michael


BR,

Jukka Zitting

Reply via email to