Hi Jukka, At first, I was hesitating to remove the IT tests. But then I realised that "tika-bundle-it" does almost nothing (i.e. "BundleTest.java" just tests a text and a PDF file).
So I've taken your advise and deleted it from my Eclipse workspace. Everything is working fine now. Thanks! p.s.: I am indeed using Eclipse Indigo and the latest m2e. On Mon, Oct 3, 2011 at 10:57 AM, Jukka Zitting <jukka.zitt...@gmail.com> wrote: > Hi, > > On Mon, Oct 3, 2011 at 4:46 PM, Nick Burch <nick.bu...@alfresco.com> wrote: >> What I tend to do is build the project with maven on the command line, then >> unpack the tika-bundle jar. >> >> Then, I add a regular (non maven) project to eclipse, and add the jars from >> the bundle as dependencies by hand. It's fiddly to do, but it doesn't >> require me to win the battle with the maven eclipse project... > > Have you tried the latest m2e version that comes with Eclipse Indigo? > Apart from the nasty plugin execution issues it works really well for > me. > > Here's how I set up a Tika checkout in Eclipse: > > Import... > Existing Maven Projects > Enter /path/to/tika > De-select tika-bundle-it because of the plugin execution issues > Click Finish > > The result is a perfectly configured set of Eclipse projects, one for > each Tika component. > > I guess we should also add some workarounds for the tika-bundle-it component. > > BR, > > Jukka Zitting > -- Sincerely, Albert Law Senior Software Engineer Logik.com
