Release 4.0.0 on August 1st

[ignazio1977]

@matthewhorridge @ansell @sesuncedu Am I right in thinking we're good to go?

[ansell]

Unfortunately I have only effectively had a week or so to do testing (due to other urgent work tasks) and didn't finish the migration of my project after working through the pull requests here. However, it looks good to me from my limited testing and reviewing the new APIs. The integration of the rio module is good to go for version 4.0.0 from my point of view, and the rest looks fairly stable.

[matthewhorridge]

I haven't had enough time to check this out due to some other deadlines. I mainly need to check compatibility with Protege. I'll will look at this by Friday.

[matthewhorridge]

I've just had a quick look and found quite a few things that would cause us problems. While I could make the changes in Protege without a problem, we're concerned about plugin breakage. I think some more wrappers will need to go in the compatibility module. I'll draw up a list.

[matthewhorridge]

I'll file these as separate issues by the way.

[ignazio1977]

I've merged a set of changes discussed with Matthew, available in RC 3

d1ea7b3

This should cover most of the points that we discussed, but there might be a few more I've missed.
Related commits:

1fe39af
035894d
6d6c6a0
db28044
86f7333

Based on this last rc, I've updated my pull requests for Protege and related dependencies:
protegeproject/xmlcatalog#2
protegeproject/protege-owlapi#4
protegeproject/protege#84

Most of the changes are trivial, but I'll let the Protege team feedback on them.

Next order of business, go through the most common Protege plugins and see if they can be built against the new stuff. Also, update the pull requests for reasoners.

List:
https://code.google.com/p/aceview/
https://code.google.com/p/co-ode-owl-plugins/
https://sourceforge.net/projects/owl2query/
https://sourceforge.net/projects/owldiff/
https://code.google.com/p/sadi/
https://github.com/aehrc/snorocket
https://code.google.com/p/skoseditor/
https://github.com/protegeproject/owlviz
https://github.com/protegeproject/dlquery

// UComp (cannot find source code for this)
https://aic.ai.wu.ac.at/~wohlg/uComp_plugin/update.properties

(cannot find the source for this one)
http://vowl.visualdataweb.org/protegevowl.html

(source seems to be available upon registration??)
http://ontop.inf.unibz.it/

[ansell]

OntoP is at:

https://github.com/ontop/ontop

[ignazio1977]

Well that's been eventful.

I've checked out the set of plugins above, and gone to work on those missing a pom build system:
aceview, co-ode-owl-plugins, skoseditor. A variety of OWLAPI versions in the bunch.

I've just got started with updating the remaining set and got the SKOS API updated and building.
The next interesting challenge will be how to get all of this built and deployed in Protege to be tested.

[ignazio1977]

The plugins mentioned above have been updated and are available on my repositories for any good soul who wishes to carry out some building and testing magic. They all compile against Protege 5 beta 16 + the OWLAPI changes available on my repositories, and OWLAPI RC 3 (might require a local build of RC3 for the latest updates)

[ignazio1977]

So, of course the first sanity test is to start Protege 5 with OWLAPI 4 and see what happens. Promptly falling face first on OSGi constraints not satisfied :-) a few build settings need updating.

[ignazio1977]

Once another set of Protege plugins was updated, and an owlapi-osgidistribution module created to get a self contained, dependencies included jar (to counteract the fact that each dependency would need to be wrapped as an OSGi compatible jar otherwise - we got more than a dozen jars in the dependencies now, so quite complicated to set up), I've managed to boot Protege without errors.

Problem is, no parsers are found. ServiceLoader and OSGi do /not/ act well together. There is a workaround here http://blog.osgi.org/2013/02/javautilserviceloader-in-osgi.html but it requires OSGi extenders that are not currently in Protege. Bit out of my OSGi comfort zone here, so I'm not sure if this can be easily fixed. I'm looking at an alternative workaround.

[ignazio1977]

Was easier than I thought - at least as long as the OWLAPI comes in a single bundled jar.

451f912

I've got a working Protege distro, anyone fancying a test drive?

https://github.com/ignazio1977/protegetests/blob/master/Protege_5.0_beta_OWLAPI_4.zip

[ignazio1977]

merry ping @matthewhorridge @ansell @sesuncedu how do you feel about the release moving on, chaps? I'm satisfied that the current version4 branch can be used for a working Protege installation.
I've not issued pull requests for all my latest changes to the various Protege and plugin projects because I can't muster the energy :-) but most of the required changes before Protege can switch officially are fairly straightforward.