http://www.apache.org/dyn/closer.cgi/tika/apache-tika-0.9.zip



On Sun, Mar 6, 2011 at 12:28 PM, Ilya Zavorin <[email protected]> wrote:
> Benson,
>
> I tried Maven 2.2.1 and got the same error.
>
> I am at the exploratory stage of my project so running a binary would be 
> fine. However, I am having a hard time locating it: all download pages I 
> found so far give me the source. Could you point me to it?
>
> If Tika does fit my needs, I might need to have access to buildable code 
> later on, but for now I'd be happy with something that I can run.
>
> Thanks,
>
>
> Mr. Ilya Zavorin, Ph.D.
> Principal Research Analyst
> Knowledge and Information Management Division
> CACI International
> 4831 Walden Lane
> Lanham, MD 20706
> ph: 1-301-306-2859
> fx: 1-301-306-8201
> [email protected]
> www.caci.com
>
>
> -----Original Message-----
> From: Benson Margulies [mailto:[email protected]]
> Sent: Sunday, March 06, 2011 12:16 PM
> To: [email protected]
> Subject: Re: error while building Tika using Maven
>
> Ilya,
>
> I don't know. The automated builds on the maven project are still maven 2.2.x.
>
> You never need to 'uninstall' maven, just fill up another directory
> with another copy.
>
> But I would also ask, why download the source and build it, instead of
> just running the binary package?
>
> This could also be windows-specific. I know you guys love Windows, but
> it's not the natural habitat of this stuff.
>
> If I were you I'd get the latest maven 2.x and see what you see.
>
> --benson
>
> On Sun, Mar 6, 2011 at 12:07 PM, Ilya Zavorin <[email protected]> wrote:
>> I just downloaded it from http://maven.apache.org/download.html, so I
>> presume 3.0.3.
>>
>>
>>
>> When you asked I just noticed that Tika’s page mentions Maven 2. Does it
>> mean that I need to uninstall Maven 3 and install the older version?
>>
>> Thanks,
>>
>>
>>
>>
>>
>> Mr. Ilya Zavorin, Ph.D.
>>
>> Principal Research Analyst
>>
>> Knowledge and Information Management Division
>>
>> CACI International
>>
>> 4831 Walden Lane
>>
>> Lanham, MD 20706
>>
>> ph: 1-301-306-2859
>>
>> fx: 1-301-306-8201
>>
>> [email protected]
>>
>> www.caci.com
>>
>>
>>
>>
>>
>> -----Original Message-----
>> From: Benson Margulies [mailto:[email protected]]
>> Sent: Sunday, March 06, 2011 12:03 PM
>> To: [email protected]
>> Subject: Re: error while building Tika using Maven
>>
>>
>>
>> What version of maven?
>>
>>
>>
>> On Sun, Mar 6, 2011 at 11:30 AM, Ilya Zavorin <[email protected]> wrote:
>>
>>> Hi,
>>
>>>
>>
>>>
>>
>>>
>>
>>> I just downloaded apache-tika-0.9-src.zip from
>>
>>> http://www.apache.org/dyn/closer.cgi/tika/apache-tika-0.9-src.zip,
>>> unzipped
>>
>>> and tried to build Tika using Maven. I used the following command:
>>
>>>
>>
>>>
>>
>>>
>>
>>> mvn -e clean install
>>
>>>
>>
>>>
>>
>>>
>>
>>> and got the following error message (I am also attaching the complete
>>> log):
>>
>>>
>>
>>>
>>
>>>
>>
>>> [ERROR] Failed to execute goal
>>
>>> org.apache.maven.plugins:maven-compiler-plugin:2.0.2:compile
>>
>>> (default-compile) on project tika-parsers: Compilation failure
>>
>>>
>>
>>> [ERROR]
>>
>>>
>>> C:\Code\ATEK\CT\apache-tika-0.9\tika-parsers\src\main\java\org\apache\tika\parser\image\ImageMetadataExtractor.java:[88,34]
>>
>>> cannot access JPEGDecodeParam
>>
>>>
>>
>>> [ERROR] -> [Help 1]
>>
>>>
>>
>>> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
>>
>>> goal org.apache.maven.plugins:maven-compiler-plugin:2.0.2:compile
>>
>>> (default-compile) on project tika-parsers: Compilation failure
>>
>>>
>>
>>>
>>> C:\Code\ATEK\CT\apache-tika-0.9\tika-parsers\src\main\java\org\apache\tika\parser\image\ImageMetadataExtractor.java:[88,34]
>>
>>> cannot access JPEGDecodeParam
>>
>>>
>>
>>>
>>
>>>
>>
>>>
>>
>>>
>>
>>>                 at
>>
>>>
>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:213)
>>
>>>
>>
>>>                 at
>>
>>>
>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
>>
>>>
>>
>>>                 at
>>
>>>
>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
>>
>>>
>>
>>>                 at
>>
>>>
>>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
>>
>>>
>>
>>>                 at
>>
>>>
>>> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
>>
>>>
>>
>>>                 at
>>
>>>
>>> org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
>>
>>>
>>
>>>                 at
>>
>>>
>>> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
>>
>>>
>>
>>>                 at
>>
>>> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319)
>>
>>>
>>
>>>                 at
>>
>>> org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
>>
>>>
>>
>>>                 at
>>> org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
>>
>>>
>>
>>>                 at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
>>
>>>
>>
>>>                 at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
>>
>>>
>>
>>>                 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
>>
>>> Method)
>>
>>>
>>
>>>                 at
>>
>>>
>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>>
>>>
>>
>>>                 at
>>
>>>
>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>
>>>
>>
>>>                 at java.lang.reflect.Method.invoke(Method.java:613)
>>
>>>
>>
>>>                 at
>>
>>>
>>> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
>>
>>>
>>
>>>                 at
>>
>>>
>>> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
>>
>>>
>>
>>>                 at
>>
>>>
>>> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
>>
>>>
>>
>>>                 at
>>
>>> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
>>
>>>
>>
>>> Caused by: org.apache.maven.plugin.CompilationFailureException:
>>> Compilation
>>
>>> failure
>>
>>>
>>
>>>
>>> C:\Code\ATEK\CT\apache-tika-0.9\tika-parsers\src\main\java\org\apache\tika\parser\image\ImageMetadataExtractor.java:[88,34]
>>
>>> cannot access JPEGDecodeParam
>>
>>>
>>
>>>
>>
>>>
>>
>>>
>>
>>>
>>
>>>                 at
>>
>>>
>>> org.apache.maven.plugin.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:516)
>>
>>>
>>
>>>                 at
>>
>>> org.apache.maven.plugin.CompilerMojo.execute(CompilerMojo.java:114)
>>
>>>
>>
>>>                 at
>>
>>>
>>> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
>>
>>>
>>
>>>                 at
>>
>>>
>>> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
>>
>>>
>>
>>>                 ... 19 more
>>
>>>
>>
>>> [ERROR]
>>
>>>
>>
>>> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
>>
>>>
>>
>>> [ERROR]
>>
>>>
>>
>>> [ERROR] For more information about the errors and possible solutions,
>>> please
>>
>>> read the following articles:
>>
>>>
>>
>>> [ERROR] [Help 1]
>>
>>> http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
>>
>>>
>>
>>> [ERROR]
>>
>>>
>>
>>> [ERROR] After correcting the problems, you can resume the build with the
>>
>>> command
>>
>>>
>>
>>> [ERROR]   mvn <goals> -rf :tika-parsers
>>
>>>
>>
>>>
>>
>>>
>>
>>> I found no info on this plugin here: http://maven.apache.org/plugins/
>>
>>>
>>
>>>
>>
>>>
>>
>>> I am doing this on an XP Pro machine.
>>
>>>
>>
>>>
>>
>>>
>>
>>> Why am I getting this error and how can I resolve this?
>>
>>>
>>
>>>
>>
>>>
>>
>>> Thanks,
>>
>>>
>>
>>>
>>
>>>
>>
>>>
>>
>>>
>>
>>> Mr. Ilya Zavorin, Ph.D.
>>
>>>
>>
>>> Principal Research Analyst
>>
>>>
>>
>>> Knowledge and Information Management Division
>>
>>>
>>
>>> CACI International
>>
>>>
>>
>>> 4831 Walden Lane
>>
>>>
>>
>>> Lanham, MD 20706
>>
>>>
>>
>>> ph: 1-301-306-2859
>>
>>>
>>
>>> fx: 1-301-306-8201
>>
>>>
>>
>>> [email protected]
>>
>>>
>>
>>> www.caci.com
>>
>>>
>>
>>>
>

Reply via email to