Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Samebug tips

  1. ,
    via GitHub by trejkaz

    There was a problem before jcommander v1.72 that you couldn't have a single main parameter (in spite of what the doc said).

Solutions on the web

via GitHub by kensipe
, 1 year ago
Was passed main parameter 'crate-mesos-0.1.0-SNAPSHOT-b74d1a0.tar.gz' but no main parameter was defined
via GitHub by kensipe
, 1 year ago
Was passed main parameter 'crate' but no main parameter was defined
via GitHub by airomega
, 1 year ago
Was passed main parameter 'password' but no main parameter was defined
via GitHub by airomega
, 1 year ago
Was passed main parameter 'password' but no main parameter was defined
via GitHub by hanizaidi110
, 2 years ago
Was passed m ain parameter 'Automation' but no main parameter was defined
via GitHub by ravindra5557
, 2 years ago
Was passed m ain parameter 'Automation' but no main parameter was defined
com.beust.jcommander.ParameterException: Was passed main parameter 'crate-mesos-0.1.0-SNAPSHOT-b74d1a0.tar.gz' but no main parameter was defined	at com.beust.jcommander.JCommander.getMainParameter(JCommander.java:903)	at com.beust.jcommander.JCommander.parseValues(JCommander.java:748)	at com.beust.jcommander.JCommander.parse(JCommander.java:279)	at com.beust.jcommander.JCommander.parse(JCommander.java:262)	at com.beust.jcommander.JCommander.(JCommander.java:207)	at io.crate.frameworks.mesos.Main.parseConfiguration(Main.java:90)	at io.crate.frameworks.mesos.Main.main(Main.java:120)