Hi,

2008/12/5 Chris Hostetter <[EMAIL PROTECTED]>

>
> : Thanks to all who provided feedback in the first attempt of 0.2 releases.
> : This release vote is based on a new 0.2 release branch based on the
> current
> : trunk following the discussions on the development list.
>
> this looks pretty good, two small things concern me...
>
> 1) the pom.xml file still refers to broken @incubator addresses for
> subscribe, unsubscribe, and post, as well as listing the main url as
> http://incubator.apache.org/tika/
>
> How do these get used by maven?  Will they confuse people?
>
> (FWIW: I'd put a patch for all of these in TIKA-178)


Sorry, I assumed this had been updated in trunk but I had taken my branch
before the update thus your patch.

Maven uses them to add information in the generated site (see
http://lucene.apache.org/tika/mail-lists.html). It would confuse people if
they via this page on the generated site locally.

Given the time it would take to fix, I would be inclined to fix it and then
create a new RC - that is as long as people have the time to check the new
RC.

>
> 2) I see the updated gettingstarted guide no longer refers to the
> "standalone" jar, but now it says that the main tika jar can be used as a
> command line util.   When i try that i get a claspath issue...
>
> $ java -jar target/tika-0.2.jar --help
> Exception in thread "main" java.lang.NoClassDefFoundError:
> org/apache/log4j/Layout
>
> is this expected?  (it makes sense given the dependencies listed, but i
> want to double check since the command line section suggests that it
> should work)


I would expect that. I added the extra bit on the end of the first paragraph
saying "provided the dependencies are on the classpath". Not sure if anyone
has any better ideas on how to flag that up.

Cheers,
Dave

Reply via email to