search

AnantLabs / dkpro-tc

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

Conflicting weka versions - Upgrade to weka 3.7.11 #212

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
I trained a weka model and saved it. This model only works when I read it with 
weka 3.7.9 and it throws an exception when I read it with 3.7.11. However, both 
dependencies seem to come in from the tc framework. I have not yet figured it 
out completely, but it seems to depend on the order of the dependencies. 
dkpro-tc-ml-weka wants 3.7.9 and meka wants 3.7.11. I use dkpro-tc 0.7-SNAPSHOT.
I have a working configuration now but I had to add dependencies to the pom 
that are not directly needed in the project. 
The problem source is not yet entirely clear to me, I just wanted to mention 
it, in case someone else faces the same issue.

Original issue reported on code.google.com by lisa.bei...@gmail.com on 26 Nov 2014 at 10:19

GoogleCodeExporter commented 9 years ago 
Right, both mulan and meka use different weka version, that are both managed to 
3.7.9 in TC
It is not fully clear to me under what circumstances this works or breaks.

However, maybe we should at least raise the managed version to 3.7.11 as things 
might be downwards compatible but probably not upwards.

Original comment by torsten....@gmail.com on 26 Nov 2014 at 10:30

GoogleCodeExporter commented 9 years ago 
I'll investigate that. Thanks for notifying.

Original comment by daxenber...@gmail.com on 26 Nov 2014 at 10:31

GoogleCodeExporter commented 9 years ago

Original comment by daxenber...@gmail.com on 26 Nov 2014 at 10:31

GoogleCodeExporter commented 9 years ago 
The exception I get is the same as described here:
http://list.waikato.ac.nz/pipermail/wekalist/2014-April/060788.html

However, in this post they explicitly say that this should not affect version 
3.7.11.

Original comment by lisa.bei...@gmail.com on 26 Nov 2014 at 11:59

GoogleCodeExporter commented 9 years ago 
After investigating the meka and mulan dependencies, I think we can upgrade the 
managed version to weka 3.7.11. This comes with a risk of incompatible old 
models, but we will have that problem sooner or later anyways, and user can 
still enforce a lower version in their projects.

Original comment by daxenber...@gmail.com on 26 Nov 2014 at 6:17

GoogleCodeExporter commented 9 years ago 
This issue was closed by revision r1265.

Original comment by daxenber...@gmail.com on 5 Dec 2014 at 10:55

GoogleCodeExporter commented 9 years ago

Original comment by daxenber...@gmail.com on 6 Dec 2014 at 10:00