René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Decide how to support logging errors and warnings","articleBody":"Many ops in the old imagej-ops framework, such as [this one](https://github.com/imagej/imagej-ops/blob/1820948f097f098878cf5d5745d39c63cf2e6049/src/main/java/net/imagej/ops/threshold/minError/ComputeMinErrorThreshold.java#L59) or [this one](https://github.com/imagej/imagej-ops/blob/1820948f097f098878cf5d5745d39c63cf2e6049/src/main/java/net/imagej/ops/threshold/rosin/ComputeRosinThreshold.java#L59) attempt to log errors or warnings. Sometimes this is in place of throwing some `RuntimeException` (as in the case of the former) or other times it is just saying something about the data (as in the case of the latter). We need to find a consistent way to deal with the situations in which we would like to pass on messages/errors.\r\n\r\nRegardless of the option, no messages should be allowed as secondary outputs.\r\n\r\n**Potential solutions:**\r\n* Use Scijava's `Logger`\r\n* Create dedicated error subclasses (although this will only solve the issues with errors, not with the logging)\r\n* Not allow any sort of logging","author":{"url":"https://github.com/gselzer","@type":"Person","name":"gselzer"},"datePublished":"2019-05-14T21:09:07.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":7},"url":"https://github.com/13/scijava/issues/13"}