Mailing-List: contact dev-help@ignite.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ignite.apache.org
Date: Sun, 5 Jun 2016 11:07:09 -0700 (PDT)
From: zshamrock <aliaksandr.kazlou@gmail.com>
To: dev@ignite.apache.org
Message-ID: <1465150029587-9281.post@n4.nabble.com>
Subject: Not supported -np (no pause) parameter for Ignite 1.6.0 release
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
archived-at: Sun, 05 Jun 2016 18:45:29 -0000

Tried to create an issue myself from Ignite JIRA, looks like I don't have
enough permissions to do it. 

So post it here:

/apache-ignite-fabric-1.6.0-bin/bin$ ./ignite.sh -np
Invalid arguments: -np
Usage:
    ./ignite.sh [?]|[path {-v}{-np}]|[-i]
    Where:
    ?, /help, -help, - show this message.
    -v               - verbose mode (quiet by default).
    -np              - no pause on exit (pause by default)
    -nojmx           - disable JMX monitoring (enabled by default)
    -i              - interactive mode (choose configuration file from
list).
    path            - path to Spring XML configuration file.
                      Path can be absolute or relative to IGNITE_HOME.
 
Spring file should contain one bean definition of Java type
'org.apache.ignite.configuration.IgniteConfiguration'. Note that bean will
be
fetched by the type and its ID is not used./

So, what if I don't have a Spring configuration file to provide, but still
want to use either -np or -v?


--
View this message in context: http://apache-ignite-developers.2346864.n4.nabble.com/Not-supported-np-no-pause-parameter-for-Ignite-1-6-0-release-tp9281.html
Sent from the Apache Ignite Developers mailing list archive at Nabble.com.