Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Message-ID: <4105352.1184315685852.JavaMail.jira@brutus>
Date: Fri, 13 Jul 2007 01:34:45 -0700 (PDT)
From: "Adrian Co (JIRA)" <jira@apache.org>
To: dev@activemq.apache.org
Subject: [jira] Resolved: (AMQ-1314) Invalid Command Line Option Handling
In-Reply-To: <17045074.1183670072855.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/activemq/browse/AMQ-1314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Adrian Co resolved AMQ-1314.
----------------------------

       Resolution: Fixed
    Fix Version/s: 5.0.0
         Assignee: Adrian Co

Fix added to the 5.0 trunk.
http://svn.apache.org/viewvc?view=rev&rev=555911

> Invalid Command Line Option Handling  
> --------------------------------------
>
>                 Key: AMQ-1314
>                 URL: https://issues.apache.org/activemq/browse/AMQ-1314
>             Project: ActiveMQ
>          Issue Type: Improvement
>          Components: Broker
>    Affects Versions: 4.1.1
>            Reporter: Joe Fernandez
>            Assignee: Adrian Co
>            Priority: Minor
>             Fix For: 5.0.0
>
>
> If the 'activemq' command is given an invalid option, it will put  out an INFO message stating that the option is invalid and thus is being ignored; however, the command will still go ahead and start the broker.
> I'd like to propose that, when given an invalid option, 'activemq' instead put out an Error message with accompanying USAGE string and *not* start the broker.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.