[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

how to start paros?



Solved now.
This was dealt with in bug  Bug#532194.
To start paros in squeeze, use

/usr/lib/jvm/java-6-sun/jre/bin/java -Duser.dir=$HOME/.paros -cp
/usr/share/java/commons-codec.jar:/usr/share/java/commons-collections3.jar:/usr/share/java/commons-configuration.jar:/usr/share/java/commons-httpclient.jar:/usr/share/java/commons-lang.jar:/usr/share/java/commons-logging.jar:/usr/share/java/log4j-1.2.jar:/usr/share/java/jdic.jar:/usr/share/java/hsqldb.jar:/usr/share/java/paros.jar
org.parosproxy.paros.Paros

See  Bug#532194 if you need details and other alternatives.

John


On Fri, Jun 5, 2009 at 10:59 PM, John O Laoi<brianolaoi@gmail.com> wrote:
> Hi
> I am using squeezef.
> I installed paros proxy  with   aptitude install paros.
> After some googleing, I found that to start Paros, I needed to use
>
> sh /usr/share/paros/startserver.sh
>
>
> This told me that it could not find the file  paros.jar,
> so I edited to the file to point to its location,
> ie I changed  the line
> java -jar  paros.jar
>  TO
> java -jar /usr/share/java/paros.jar
>
> Now, I am getting the following error:
>
> $ sh   /usr/share/paros/startserver.sh
> Exception in thread "main" java.lang.NoClassDefFoundError:
> org/apache/commons/httpclient/protocol/ProtocolSocketFactory
> Caused by: java.lang.ClassNotFoundException:
> org.apache.commons.httpclient.protocol.ProtocolSocketFactory
>        at java.net.URLClassLoader$1.run(URLClassLoader.java:217)
>        at java.security.AccessController.doPrivileged(Native Method)
>        at java.net.URLClassLoader.findClass(URLClassLoader.java:205)
>        at java.lang.ClassLoader.loadClass(ClassLoader.java:323)
>        at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:294)
>        at java.lang.ClassLoader.loadClass(ClassLoader.java:268)
>        at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:336)
> Could not find the main class: org.parosproxy.paros.Paros. Program will exit.
>
> Any ideas?
>
> John
>


Reply to: