initializeDynet transparently

[MihaiSurdeanu]

Call initializeDynet in the c'tor for CluProcessor rather than explicitly in the code.

[kwalcock]

Processors has a PR to do this. However, to use it with habitus, processors would normally need to be republished. There are some other habitus-related changes to processors that probably aren't ready to publish without a little more real-life testing, mostly because unpublishing is next to impossible. I'm thinking of the Odin-related bug fix in particular #673. I would like to modify habitus to use the main, not yet published branch of processors to get in more testing before publishing. Habitus is the project that is most able to observe problems that might arise. So, I would go ahead and merge PRs to processors and then modify habitus to use the changes, but hold off on the publishing. This would be achieved by having habitus use the jitpack resolver ("jitpack" at "https://jitpack.io") as done in other projects. FYI @MihaiSurdeanu, @maxaalexeeva.

[MihaiSurdeanu]

Makes sense. Also, habitus people can just publishLocal for now.

[kwalcock]

jitpack seems unable to build processors. I will try artifactory instead.