[ https://issues.apache.org/jira/browse/TIKA-1273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tyler Palsulich resolved TIKA-1273. ----------------------------------- Resolution: Fixed The server now starts as expected. So, I'm marking this as Fixed. {code} ➜ trunk java -jar tika-server/target/tika-server-1.8-SNAPSHOT.jar Mar 20, 2015 3:53:04 PM org.apache.tika.server.TikaServerCli main INFO: Starting Apache Tika 1.8-SNAPSHOT server Mar 20, 2015 3:53:04 PM org.apache.cxf.endpoint.ServerImpl initDestination INFO: Setting the server's publish address to be http://localhost:9998/ Mar 20, 2015 3:53:04 PM org.slf4j.impl.JCLLoggerAdapter info INFO: jetty-8.y.z-SNAPSHOT Mar 20, 2015 3:53:04 PM org.slf4j.impl.JCLLoggerAdapter info INFO: Started SelectChannelConnector@localhost:9998 Mar 20, 2015 3:53:04 PM org.apache.tika.server.TikaServerCli main INFO: Started {code} > old tika-server jar artifact contains no manifest so not able to invoke from > shell > ---------------------------------------------------------------------------------- > > Key: TIKA-1273 > URL: https://issues.apache.org/jira/browse/TIKA-1273 > Project: Tika > Issue Type: Bug > Components: server > Affects Versions: 1.5 > Reporter: Lewis John McGibbney > Priority: Minor > Fix For: 1.8 > > > I've never ever used the old tika-server artifact which is generated when one > installs the server module. It needs to contain a manifest otherwise it > cannot be invoked from the shell. -- This message was sent by Atlassian JIRA (v6.3.4#6332)