> Is there a particular reason you suggested using FluoExceptions and not > AlreadyInitializedExceptions?
No, I would be in favor of using AlreadyInitializedException when appropriate. I think the main thing I was thinking about was not calling System.exit. Its ok for command to call System.exit, but API impls should not. > What is the reason for the nested try blocks in the remove and init Fluo > Commands? I do not know of a reason to keep these. Seems like the catch could be moved to the surrounding try. > However it will only do this if there isn't an application already running? Yeah, the update should not happen if the app is running. [ Full content available at: https://github.com/apache/fluo/issues/1003 ] This message was relayed via gitbox.apache.org for [email protected]
