Page Contents


Feature List

Previous topic

Developer Documentation

Next topic

Installing OMERO from source

This Page


This documentation is for the new OMERO 5.2 version. See the latest OMERO 5.1.x version or the previous versions page to find documentation for the OMERO version you are using if you have not upgraded yet.

What’s new for OMERO 5.2 for developers

  • The Version requirements section provides extensive details about which operating systems and dependency versions we intend to support for the life of 5.2 and the likely changes to these for the next major release (currently planned to be 5.3). Most notably for development purposes, we have dropped support for Java 1.6.

Breaking changes


OMERO.web has undergone a major upgrade, updating jsTree to version 3.0.8 and using json for all tree loading to substantially improve performance.

If you have web code that directly works with the jsTree, you will need to update it according to the jsTree docs.

A number of new URLs are available in webclient, with the /api/ prefix that provide json data for the jsTree. However, these may soon be moved to a different Django app and should not yet be considered stable.


The API’s request operations Chmod, Chgrp, Chown, Delete, and their superclass GraphModify, were deprecated in 5.1 and will be removed in 5.3. They are replaced by Chmod2Chgrp2, Chown2, Delete2, and their superclass GraphModify2. OMERO developers who have not migrated yet should refer to Using the new 5.1 graph requests and take action before the deprecated features are removed.

Java Gateway

The Java gateway has undergone a major overhaul. This should make the development of Java applications much easier. We do not intend to modify the methods already available but this work should still be considered as under development. Feedback as always is welcome. See OMERO Java language bindings for more information or follow the example in minimal-omero-client.

OMERO model

The Rect class has been renamed to Rectangle to match the OME-XML schema. This requires the corresponding change to be made in client software that uses the OMERO.blitz server API to work with ROIs.