Add integration test for CLI import as functionality
Refactor sudo_args and add failing test for multi-group CLI import as
Mark multi-group import as test as xfail
Add failing to test for regular import in multi-group
Keep smart folders when sorting. (see #12294)
Remove commented code and comments

No longer required.
Make sure the smart folder is always at the bottom.
Merge pull request #2588 from sbesson/rebased/develop/cli_importsudo

Add integration tests for CLI import as (rebased onto develop)
Fixed a NPE
Merge pull request #2598 from jburel/rebased/develop/orphaned-missing

Orphaned missing (rebased onto develop)
Reduce memoizer wait to 0 (Fix #10337)

For relatively fast setId alls, no bfmemo file
was being produced. Lowering this value to zero
shaved off 1/3 of the setId time, though, even
for fast files.

This should also prevent discrepancies when the
system is underload: now a memo file will always
be produced.
Nearly working artifactory publish

The artifactory-publish resolver can now be used
from the `release-hudson` target to publish all
the OMERO jars to the OME artifactory repo. The
only parameter needed is a password for hudson.
Override 'artifactory' target in insight

Since insight does not produce all the artifacts
upfront, the target needs to be overwritten like
the `install` target and "haltonmissing" passed.
Omit Bio-Formats component

Since Bio-Formats jars/poms are pushed via
a separate job, the release-hudson target
will now skip that component.
Make repository name configurable

Now, by using `ant release-hudson -Dartifactory.repository=foo`
or setting the same in etc/local.properties a repository other
than ome.staging can be used. Most useful is setting it to
ome.unstable for merge builds or ome.snapshots for latest builds.
Make artifactory username configurable
changingPattern is now SNAPSHOT not DEV
Load local properties last (overwrite)
Add classifier to publish resolver
Don't publish ivy files (workaround)

For some reason, the ivy.xml files are being uploaded
with "SNAPSHOT" in their names rather than with the
artifactory-specific timestamp. This requires the user
having the "delete" permission, so instead, we're
holding back that artifact.