TRACER
  • Introduction
  • Manual
    • About the manual
    • Introduction
      • Text Reuse
      • TRACER overview
    • System prerequisites
    • Download and installation
    • Corpus preparation
    • PoS-tagging, lemmatisation & WordNets
    • Configuration
      • Step 1. Preprocessing
      • Step 2. Featuring/Training
      • Step 3. Selection
      • Step 4. Linking
      • Step 5. Scoring
    • Execution of TRACER
    • Postprocessing
    • Results & computed files
    • Keeping a detection logbook
    • Limitations
    • References
  • Beta
    • Visualising results in a tabular format
    • BabelNet API
    • Text preprocessing automation
  • Support
    • Troubleshooting
      • Unable to parse date
      • Unable to access jarfile
      • Empty score and link files
      • Java lang no class definition found
      • Out of memory
      • Out of bounds exception
      • Windows: length of folder name
      • Windows: PowerShell
    • FAQ
    • Publications
    • Resources
    • Command line: MAC vs. Windows
Powered by GitBook
On this page
  1. Support
  2. Troubleshooting

Unable to access jarfile

PreviousUnable to parse dateNextEmpty score and link files

Last updated 7 years ago

CtrlK

When compiling TRACER with Apache Ant, it is important you use the command ant *only* and not ant verbose or other Ant commands. Although using ant verbose or similar will produce a successful build of TRACER, the execution of TRACER after this build will return the following error:

C:\Users\*anonymous*\Downloads\tracer>java -Xmx600m -Deu.etrap.medusa.config.ClassConfig=conf/tracer_config.xml -jar tracer.jar

Error: Unable to access jarfile tracer.jar

This is because the tracer.jar file generated from the Ant build is not complete (it should be some 33MB in size).