Hi Chris,

See here:

http://ci.apache.org/builders/tika-trunk/builds/46/steps/compile/logs/stdio

This has to do with the issue of the tika-core jar which Ken's patch updated not being used and an older (likely previous nightly) SNAPSHOT being used. Maybe we should update the builder to do an mvn install at the tika root before doing e.g., an mvn test? Jukka, do you have enough karma to do this? Or, if you teach me I'd be happy to learn...

Thanks for digging into this.

The tika-core sources are being built before the tika-parsers sources, since tika-parsers has a dependency on tika-core, and Maven's reactor then orders things properly.

But the tika-core jar isn't being deployed before the tika-parsers sources are compiled, which creates this problem.

It feels like there's a simple, elegant Maven-esque solution, but my hack idea is to do a mvn clean install for core first.

-- Ken

On 7/8/10 10:56 AM, "build...@apache.org" <build...@apache.org> wrote:

The Buildbot has detected a new failure of tika-trunk on ASF Buildbot.
Full details are available at:
http://ci.apache.org/builders/tika-trunk/builds/46

Buildbot URL: http://ci.apache.org/

Buildslave for this Build: isis_ubuntu

Build Reason:
Build Source Stamp: [branch tika/trunk] 961850
Blamelist: kkrugler

BUILD FAILED: failed compile

sincerely,
-The Buildbot

--------------------------------------------
Ken Krugler
+1 530-210-6378
http://bixolabs.com
e l a s t i c   w e b   m i n i n g




Reply via email to