Use brew test command for displaying OMERO/Bio-Formats versions
Add OMERO.web config/startup using nginx to the Homebrew script
Fix directory type and stop nginx
Fix OMERO.web stop, add config and stop server
Add simple test for Web connection
Test Web connection using wget
Install nginx as part of the OMERO formula
Allow to set HTTP port by environment  variable

Although the script seems to run fine locally, it appears to conflict in a
Jenkins environment which is also using port 8080. This allows to control the
HTTP port for OMERO.web testing.
Fix variable substitution
Fix typo
Fix (yet another time) the Homebrew installation one-liner
CLI admin diagnostics: only check readability of var folder

In a multi-user environment where group members have permissions to read but
not write the var/ folder of the server, bin/omero admin diagnostics currently
fails with a "Cannot access" exception. This commit relaxes the check_access()
condition of the diagnostics subcommand to check the folder (and subfolders)
readability only.
Customise Windows service name: omero.windows.servicename
Don't block 'batch annotate' panel even if canAnnotate() is False
OmeroCpp: Disable remaining integration search test
OMERO5.1DEV__12: modify experimenter and password.

This commit drops the "dn" column from the "password" table
and adds update scripts for adding an "ldap" column to "experimenter"
and setting it to the correct value based on "dn".
setDN() uses a boolean flag instead of string.

This changes the method declaration to accept a boolean instead
of the new DN string. The change happens on the "experimenter"
table ("ldap" column) and not on "password".
SqlAction.java: Remove unused actions, add new.

This removes actions that relied on the "dn" column of the
"password" table and also add surrogate actions that make use
of the new "ldap" column.
PasswordUtil.java: Use updated SQL action.

This simplifies the usage of PasswordUtil and the logic in AdminImpl
and ResetPasswordRequestI.
LdapImpl.java: Update method logic.

This is due to the updates to SQL actions and also the now
available new direct way of checking if a user came from an LDAP
server.