search

dkpro / dkpro-tc

UIMA-based text classification framework built on top of DKPro Core and DKPro Lab.
https://dkpro.github.io/dkpro-tc/
Other
34 stars 19 forks source link

Broken tests in dkpro-tc-features-readability #218

Closed daxenberger closed 8 years ago

daxenberger commented 9 years ago

Originally reported on Google Code with ID 218

Most of the tests in dkpro-tc-features-readability are failing (currently ignored).
@Lisa: could you please have a look at what might be going wrong here?

Reported by daxenberger.j on 2014-12-04 14:13:19

daxenberger commented 9 years ago 
This issue was updated by r1250 and subsequent. However, some tests still fail.

Reported by daxenberger.j on 2014-12-04 15:15:59

daxenberger commented 9 years ago 
No tests are failing atm, but I am not sure whether they are all doing what they are
supposed to. Leaving this open for now.

Reported by daxenberger.j on 2014-12-11 09:08:53

daxenberger commented 9 years ago 
dkpro-tc-features-readability will probably be excluded from the next release.

Reported by daxenberger.j on 2014-12-11 15:49:39

daxenberger commented 9 years ago 
This issue was updated by revision r1422.

Replacing GPL dependency (berkeley parser) with ASL dependency (Malt parser).
This breaks a number of tests, which are currently ignored. 
One of the developers, please have a look.

Reported by daxenberger.j on 2015-04-08 15:44:38

daxenberger commented 9 years ago 
This issue was updated by revision r1423.

deleting resources and related feature extractors with unclear license.

Reported by daxenberger.j on 2015-04-08 15:45:39

Horsmann commented 8 years ago

@how-ever-fixes-this Once the test-cases are working please remove the property from the pom.xml that excludes this project from being released

Horsmann commented 8 years ago

@zesch @daxenberger Are there any real plans to fix this issue or can we dump the dead code project?

zesch commented 8 years ago

Most of these features are now used in other projects e.g. the cTest generation. They have been refactored there, so I guess we should remove them.

daxenberger commented 8 years ago

I guess this module will not be further developed. Has been excluded from previous releases and should be excluded from the next one. From my side, it can also be deleted in the snapshot.

Horsmann commented 8 years ago

ok. I delete the project then.