Github user revans2 commented on a diff in the pull request:

    https://github.com/apache/incubator-storm/pull/117#discussion_r14267820
  
    --- Diff: storm-core/src/jvm/backtype/storm/command/Monitor.java ---
    @@ -0,0 +1,197 @@
    +/**
    + * Licensed to the Apache Software Foundation (ASF) under one
    + * or more contributor license agreements.  See the NOTICE file
    + * distributed with this work for additional information
    + * regarding copyright ownership.  The ASF licenses this file
    + * to you under the Apache License, Version 2.0 (the
    + * "License"); you may not use this file except in compliance
    + * with the License.  You may obtain a copy of the License at
    + *
    + * http://www.apache.org/licenses/LICENSE-2.0
    + *
    + * Unless required by applicable law or agreed to in writing, software
    + * distributed under the License is distributed on an "AS IS" BASIS,
    + * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
    + * See the License for the specific language governing permissions and
    + * limitations under the License.
    + */
    +package backtype.storm.command;
    +
    +import backtype.storm.generated.*;
    +import backtype.storm.utils.NimbusClient;
    +import backtype.storm.utils.Utils;
    +import org.kohsuke.args4j.CmdLineException;
    +import org.kohsuke.args4j.CmdLineParser;
    +import org.kohsuke.args4j.Option;
    +
    +import java.util.Map;
    +
    +public class Monitor {
    +    @Option(name="--help", aliases={"-h"}, usage="print help message")
    --- End diff --
    
    Can we separate out the argument parsing from the monitor class.  The rest 
of the code uses clojure.tools.cli and I think it would be more consistent to 
use that then add in a new dependency.  It would also allow the Monitor class 
to be separated out to be used as a library.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---

Reply via email to