search

vnadgir / dkpro-core-asl

Automatically exported from code.google.com/p/dkpro-core-asl
0 stars 0 forks source link

Treetagger scripts builder error #565

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?

On the current trunk, trying to bundle the treetagger models fails.

>execute ant local-maven

BUILD FAILED
de.tudarmstadt.ukp.dkpro.core-asl\de.tudarmstadt.ukp.dkpro.core.treetagger-asl\s
rc\scripts\build.xml:31: The following error occurred while execut
ing this line:
de.tudarmstadt.ukp.dkpro.core-asl\de.tudarmstadt.ukp.dkpro.core.treetagger-asl\s
rc\scripts\build.xml:50: Can't get http://www.cis.uni-muenchen.de/
~schmid/tools/TreeTagger/data/bulgarian-par-linux-3.1.bin.gz to 
de.tudarmstadt.ukp.dkpro.core-asl\de.tudarmstadt.ukp.dkpro.core.treetagger-asl\t
ar
get\download\bulgarian-par-linux-3.1.bin.gz

What is the expected output? What do you see instead?

It should download the trained models

What version of the product are you using? On what operating system?
trunk

Please provide any additional information below.

Looks like the bulgarian-par-linux file has been upgraded to 3.2

E.g.
http://www.cis.uni-muenchen.de/~schmid/tools/TreeTagger/data/bulgarian-par-linux
-3.2-utf8.bin.gz

On
http://www.cis.uni-muenchen.de/~schmid/tools/TreeTagger/#Linux

Original issue reported on code.google.com by jkirschn...@gmail.com on 10 Dec 2014 at 2:46

GoogleCodeExporter commented 9 years ago 
Thanks for reporting the problem. I'm afraid, we only update the build.xml file 
for releases. 
We do not retroactively fix them for past releases.

The Bulgarian model has been updated in the commit r3072 to SVN trunk.

If you are using DKPro Core 1.7.0, you can use the latest build.xml from DKPro 
1.8.0-SNAPSHOT from here:

https://dkpro-core-asl.googlecode.com/svn/de.tudarmstadt.ukp.dkpro.core-asl/trun
k/de.tudarmstadt.ukp.dkpro.core.treetagger-asl/src/scripts/build.xml

If you are using earlier version, you can still try it. Please mind that you 
need to explicitly add the models to your Maven pom.xml - autoloading only 
works for model versions known at the time of the release.

Original comment by richard.eckart on 10 Dec 2014 at 3:20

GoogleCodeExporter commented 9 years ago

Original comment by richard.eckart on 22 Jan 2015 at 10:52