Hi Chris,
Wait, I think the issue is that the 'site' target triggers the
compilation of the sources, before the jars are built.
Yup, just found a good description - it's a Maven bug:
http://jira.codehaus.org/browse/MNG-2979
I believe it would work to do "mvn clean install" and then "mvn site"
And supposedly it's been fixed in Maven 3.0
-- Ken
On Jul 8, 2010, at 11:00am, Mattmann, Chris A (388J) wrote:
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...
Cheers,
Chris
On 7/8/10 10:56 AM, "[email protected]" <[email protected]> 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
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Chris Mattmann, Ph.D.
Senior Computer Scientist
NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
Office: 171-266B, Mailstop: 171-246
Email: [email protected]
WWW: http://sunset.usc.edu/~mattmann/
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Adjunct Assistant Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
--------------------------------------------
<http://ken-blog.krugler.org>
+1 530-265-2225
