java.io.IOException

Unable to resolve "edu/stanford/nlp/models/lexparser/englishPCFG.ser.gz" as either class path, filename or URL

Samebug tips0

We couldn't find tips for this exception.

Don't give up yet. Paste your full stack trace to get a solution.

Solutions on the web40

  • via GitHub by emhill
    ,
  • via Unknown by Unknown author,
  • via Stack Overflow by SahelSoft
    ,
  • Stack trace

    • java.io.IOException: Unable to resolve "edu/stanford
    • lp/models/lexparser/englishPCFG.ser.gz" as either class path, filename or URL at edu.stanford.nlp.io.IOUtils.getInputStreamFromURLOrClasspathOrFileSystem(IOUtils.java:448) at edu.stanford.nlp.io.IOUtils.readerFromString(IOUtils.java:575) at edu.stanford.nlp.parser.lexparser.LexicalizedParser.getParserFromTextFile(LexicalizedParser.java:562) at edu.stanford.nlp.parser.lexparser.LexicalizedParser.getParserFromFile(LexicalizedParser.java:425) at edu.stanford.nlp.parser.lexparser.LexicalizedParser.loadModel(LexicalizedParser.java:182) at edu.stanford.nlp.parser.lexparser.LexicalizedParser.loadModel(LexicalizedParser.java:161) at edu.purdue.cs.toydroid.bidtext.analysis.TextAnalysis.check(TextAnalysis.java:230) at edu.purdue.cs.toydroid.bidtext.analysis.TextAnalysis.analyze(TextAnalysis.java:156) at edu.purdue.cs.toydroid.bidtext.analysis.AnalysisUtil.dumpTextForSink(AnalysisUtil.java:180) at edu.purdue.cs.toydroid.bidtext.analysis.AnalysisUtil.dumpTextForSinks(AnalysisUtil.java:123) at edu.purdue.cs.toydroid.bidtext.TextLeak.analyze(TextLeak.java:267) at edu.purdue.cs.toydroid.bidtext.TextLeak.call(TextLeak.java:165) at edu.purdue.cs.toydroid.bidtext.TextLeak.call(TextLeak.java:55) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745)

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    Unknown visitor
    Unknown visitorOnce,
    Unknown visitor
    Unknown visitorOnce,
    Unknown visitor
    Unknown visitorOnce,
    Unknown visitor
    Unknown visitorOnce,