RFE: deprecation warnings

[mtbcarroll]

The OMERO 5.x builds are full of deprecation warnings such as,

/Users/mark/src/openmicroscopy/components/blitz/generated/omero/api/_GatewayTie.java:173: warning: [deprecation] getPixels(long,Current) in _GatewayOperations has been deprecated
    getPixels(long pixelsId, Ice.Current __current)
    ^

and

DEPRECATED: 'ivy.conf.file' is deprecated, use 'ivy.settings.file' instead

These rather obscure the more illuminating messages hidden among them all and may often be pointing to matters that we ought to actually be fixing.

It would be wonderful if we could review these warnings and figure out what's going on and, where possible, make corrections or improvements accordingly, reserving tactics like @SuppressWarnings("deprecation") to being a thoughtfully applied last resort.

[ajpatterson]

As a short term hack you can filter the output using sed:

./build.py | sed '/deprecation/{N;N;d;}'

[jamoore]

Removing me as owner. *Very* interested to have these fixed too though. FYI:

• The deprecated warnings are from the Ice generated code. I've filed a Bug/RFE with ZeroC, but that of course hasn't gotten us far. One option would be to add a pre-processing step of the generated files to strip out the declarations. Alternatively, if anyone can find the magic compiler flags, by all means. I've looked though.
• The Ivy warning is annoying, but I've also tried multiple times to make it go away. A newer version of Ivy may have fixed the issue if anyone would like to check that out.

[mtbcarroll]

Ah, yes, thanks, your comment on the _*Tie.java files at ​http://www.zeroc.com/forums/comments/4155-possibly-remove-deprecation-generated-_-tie-java-class.html -- perhaps it's time for a "how's that been going then?" (-:

[sbesson]

The Ivy deprecation warning has been fixed with ​https://github.com/openmicroscopy/openmicroscopy/commit/13cf6f6581f4e45af0f13cc4f9108c15de4aca08