Andrei Petrov created JENA-322:
----------------------------------

             Summary: rupdate requires commoms-loggings
                 Key: JENA-322
                 URL: https://issues.apache.org/jira/browse/JENA-322
             Project: Apache Jena
          Issue Type: Bug
          Components: ARQ
    Affects Versions: Jena 2.7.3, ARQ 2.9.3
         Environment: SL 6.3 x86_64
            Reporter: Andrei Petrov
            Priority: Minor


rupdate exception 


Exception in thread "main" java.lang.NoClassDefFoundError: 
org/apache/commons/logging/LogFactory
        at 
org.apache.http.impl.client.AbstractHttpClient.<init>(AbstractHttpClient.java:182)
        at 
org.apache.http.impl.client.DefaultHttpClient.<init>(DefaultHttpClient.java:150)
        at org.openjena.riot.web.HttpOp.execHttpPost(HttpOp.java:206)
        at org.openjena.riot.web.HttpOp.execHttpPost(HttpOp.java:154)
        at org.openjena.riot.web.HttpOp.execHttpPost(HttpOp.java:128)
        at 
com.hp.hpl.jena.sparql.modify.UpdateProcessRemote.execute(UpdateProcessRemote.java:60)
        at arq.rupdate.exec(rupdate.java:97)
        at arq.rupdate.exec(rupdate.java:82)
        at arq.cmdline.CmdMain.mainMethod(CmdMain.java:101)
        at arq.cmdline.CmdMain.mainRun(CmdMain.java:63)
        at arq.cmdline.CmdMain.mainRun(CmdMain.java:50)
        at arq.rupdate.main(rupdate.java:44)
Caused by: java.lang.ClassNotFoundException: 
org.apache.commons.logging.LogFactory
        at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
        at java.security.AccessController.doPrivileged(Native Method)
        at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
        at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
        ... 12 more

Putting commons-logging.1.1.1.jar into lib directory fixes the problem


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to