Bug #2604

RCP: 0.8.0, TreeTagger availability test stops the annotation save step

Added by Matthieu Decorde over 4 years ago. Updated about 3 years ago.

Status:New Start date:07/08/2019
Priority:Normal Due date:
Assignee:- % Done:

80%
Category:Annotation Spent time: -
Target version:TXM 0.8.0

Description

Saving annotations deletes the corpus, if :
- treetagger is not installed
- corpus has been annotated with TreeTagger

Enregistrement de 1618 annotations...
Annotations enregistrées.
** Erreur : l'annotation treetagger n'est pas possible. Veuillez vérifier les préférences de la page TXM > Avancé > TAL > TreeTagger. Abandon.
Stacktrace:
[1]  org.txm.groovy.core.GroovyScriptedImportEngine.  _build GroovyScriptedImportEngine.java, 60
[2]       org.txm.core.engines.ScriptedImportEngine.   build ScriptedImportEngine.java, 56
[3]                         org.txm.objects.Project._compute Project.java, 320
[4]                  org.txm.core.results.TXMResult. compute TXMResult.java, 2224
[5]                  org.txm.core.results.TXMResult. compute TXMResult.java, 2143
[6]   org.txm.rcp.commands.workspace.UpdateCorpus$2.     run UpdateCorpus.java, 76

Solution

Disable TreeTagger installation test if the corpus is being updated.

History

#1 Updated by Matthieu Decorde over 4 years ago

  • Description updated (diff)

#2 Updated by Matthieu Decorde over 4 years ago

  • % Done changed from 0 to 80

#3 Updated by Matthieu Decorde about 3 years ago

  • Subject changed from RCP: 0.8.0, TreeTagger avaibility test stops the annotation save stop to RCP: 0.8.0, TreeTagger avaibility test stops the annotation save step

#4 Updated by Serge Heiden about 3 years ago

  • Subject changed from RCP: 0.8.0, TreeTagger avaibility test stops the annotation save step to RCP: 0.8.0, TreeTagger availability test stops the annotation save step

Also available in: Atom PDF