unexpected behaviour

[Christopher Chilcott <ch...@au1.ibm.com>]

Hi,

I did a build of apache-tika-0.1-incubating using the maven "mvn install"
command.  The Getting Started guide says the build should produce 3
artifacts:
      tika-x.y.jar
      tika-x.y-standalone.jar (available since 0.3)
      tika-x.y-jdk14.jar (available since 0.3)

That was not what I got.  I got one artifact - tika-0.1-incubating.jar

When I try to execute the jar file (e.g. java -jar tika-0.1-incubating.jar
-?  (or with any other argument)), I get the error

"Failed to load Main-Class manifest attribute ......".

As expected with this error, the MANIFEST.MF in the jar file does not
include a Main Class specification, so the java runtime cannot find an
entry point into the jar file.

Can anyone suggest what I have done wrong? and how I correct this?

Cheers

Chris Chilcott
Senior IT Specialist
IBM Information Management
Sydney, Australia
Mail : chlcottc@au1.ibm.com
Mobile: 0413 073 936

Re: unexpected behaviour

[Jukka Zitting <ju...@gmail.com>]

Hi,

On Tue, Dec 2, 2008 at 10:19 PM, Christopher Chilcott
<ch...@au1.ibm.com> wrote:
> I did a build of apache-tika-0.1-incubating using the maven "mvn install"
> command.  The Getting Started guide says the build should produce 3
> artifacts:
>      tika-x.y.jar
>      tika-x.y-standalone.jar (available since 0.3)
>      tika-x.y-jdk14.jar (available since 0.3)
>
> That was not what I got.  I got one artifact - tika-0.1-incubating.jar

See the "available since 0.3" note. The extra artifacts will be
included in Tika 0.3 when its released. Until that you can get them by
building a checkout of the Tika trunk in svn.

BR,

Jukka Zitting