Update to OWLAPI 4.5.6

[beckyjackson]

See #308

[jamesaoverton]

@cmungall This should fix #308 and enables a feature I would like #185.

Protégé is still on 4.2.8 https://github.com/protegeproject/protege/blob/master/pom.xml#L131

Do you think we should update?

[cmungall]

cc @matthewhorridge, I made a PR on the Protege repo but I'm guessing there are other considerations besides passing travis, all plugins need to be compatible.

I feel that there are some subtle obo format reordering changes going between 4.2.x and 4.3.x and above, when there are multiple axiom annotations. I will investigate.

[matthewhorridge]

@cmungall I'm looking into this... there are some class loading issues that prevent Protege from starting and right now I don't know whether I'm doing something wrong or whether it's new custom DI mechanism in the OWL API that doesn't play nicely with OSGi. Let me know how you get on with the ordering changes.

[matthewhorridge]

Copying in @ignazio1977

[cmungall]

Thanks everyone. I'm guessing this won't make it into Protege 5.5?

Even so I think it's OK for you to go ahead if you need this @rctauber, on projects that need parity between owlapi versions, I think we can manage this by pinning to the current robot release/docker for an interim period.

[matthewhorridge]

I'm guessing this won't make it into Protege 5.5?

It will. Still in the beta period and, although this is a major change, I think it's important.

[matthewhorridge]

We'll do a few more tests here and then I'll merge in the owlapi-4.5.5 branch

[jamesaoverton]

Protege moved to 4.5.6 (protegeproject/protege#800), so let's match that.

[beckyjackson]

Switched to v4.5.6