Deprecated API
Contents
-
InterfaceDescriptionuse
CommandLine.IHelpCommandInitializable2
insteadUseCommandLine.IExecutionStrategy
instead.useCommandLine.IExecutionStrategy
instead, seeCommandLine.execute(String...)
-
ClassDescription
-
FieldDescriptionuse
CommandLine.Range.isVariable()
insteaduseCommandLine.Range.max()
insteaduseCommandLine.Range.min()
instead
-
MethodDescriptionuse
BindingContext.bind(Object, Class)
insteaduseParameterBinder.bindValue(BindingContext, Object, Class)
instead. Older code can use the CompatBinder to as a simple way of avoiding the deprecation warning and conforming to the new APIuseIdentifiedCollection.get(String, ProblemSink)
instead to make sure any warnings get picked upuse getParameterSet() insteaduse the new ExtensionPoint API instead. We should start moving Features across to that as and when we touch them.use adduseCommandLine.execute(String...)
instead, and callSystem.exit()
in the application.useCommandLine.AbstractHandler.colorScheme()
insteaduseCommandLine.setErr(PrintWriter)
andCommandLine.execute(String...)
insteaduseCommandLine.setOut(PrintWriter)
andCommandLine.execute(String...)
insteaduseCommandLine.execute(String...)
andCommandLine.getExecutionResult()
insteaduseCommandLine.execute(String...)
andCommandLine.getExecutionResult()
insteaduseCommandLine.execute(String...)
andCommandLine.getExecutionResult()
insteaduseCommandLine.execute(String...)
andCommandLine.getExecutionResult()
insteaduseCommandLine.execute(String...)
andCommandLine.getExecutionResult()
insteaduseCommandLine.execute(String...)
andCommandLine.getExecutionResult()
insteaduseCommandLine.execute(String...)
andCommandLine.getExecutionResult()
insteaduseCommandLine.execute(String...)
andCommandLine.getExecutionResult()
insteaduseCommandLine.Help.Ansi.Text.concat(String)
insteaduseCommandLine.Help.Ansi.Text.concat(Text)
insteaduseCommandLine.Help.synopsis(int)
insteaduseCommandLine.Help.TextTable.textAt(int, int)
insteaduseCommandLine.execute(String...)
andCommandLine.getExecutionResult()
insteaduseCommandLine.execute(String...)
andCommandLine.getExecutionResult()
insteaduseCommandLine.execute(String...)
andCommandLine.getExecutionResult()
insteaduseCommandLine.execute(String...)
andCommandLine.getExecutionResult()
insteadMost applications should not change the default. The rare application that does need to split parameter values without respecting quotes should useCommandLine.Model.ParserSpec.splitQuotedStrings(boolean)
.UseCommandLine.Model.ArgSpec.description()
insteaduseCommandLine.Model.ArgSpec.setValue(Object)
instead. This was a design mistake.useCommandLine.parseArgs(String...)
insteadnz.org.riskscape.picocli.CommandLine.parseWithHandler(CommandLine.IParseResultHandler2<R>, String[]) useCommandLine.execute(String...)
andCommandLine.getExecutionResult()
insteaduseCommandLine.execute(String...)
andCommandLine.getExecutionResult()
insteaduseCommandLine.execute(String...)
andCommandLine.getExecutionResult()
insteaduseCommandLine.execute(String...)
andCommandLine.getExecutionResult()
insteaduseCommandLine.executeHelpRequest(ParseResult)
insteaduseCommandLine.executeHelpRequest(ParseResult)
insteaduseCommandLine.printHelpIfRequested(ParseResult)
insteaduseCommandLine.Range.defaultArity(Field)
insteaduseCommandLine.execute(String...)
insteaduseCommandLine.execute(String...)
insteaduseCommandLine.execute(String...)
insteaduseCommandLine.execute(String...)
insteaduseCommandLine.execute(String...)
insteaduseCommandLine.execute(String...)
insteaduseCommandLine.execute(String...)
insteaduseCommandLine.execute(String...)
insteadMost applications should not change the default. The rare application that does need to split parameter values without respecting quotes should useCommandLine.Model.ParserSpec.splitQuotedStrings(boolean)
.use the ProblemCode-based constructor insteaduse the ProblemCode-based constructor insteaduse the ProblemCode-based constructor insteaduse the ProblemCode-based constructor insteaduse the ProblemCode-based constructor insteaduse the ProblemCode-based constructor insteaduse the ProblemCode-based constructor insteaduse the ProblemCode-based constructor insteadFor new code, use the i18n Problem-based method below insteaduse getMemberName instead - the AST is no longer responsible for supplying a default member name to use when the user doesn't supply one
-
ConstructorDescriptionUse
RiskscapeException(Problem)
instead to produce an internationalizable error message that works with riskscape's problem APIXXX do we want to split up the hierarchy somewhat in to : a) unexpected errors that are probably not recoverable/fixable and b) exceptions that are "semantic vessels for a problem" such as a NoSuchObjectExistsException - these things help us with flow control / where they serve as sort of case classes where a standard
ResultOrProblems
isn't sufficient, e.g. we need to do something different depending on the type ofProblem
. More thinking required...UseRiskscapeException(Problem, Throwable)
instead to produce an internationalizable error message that works with riskscape's problem APIuseRSList.create(Type)
instead - reduces the amount of identical types being allocated All Riskscape code has been ported to use create, but there may be functions etc out there that are using this old constructor. We might want to log a stack trace when this is used if it becomes functionally important that the new static constructor be used.usepicocli.CommandLine.Help#Help(picocli.CommandLine.Model.CommandSpec, picocli.CommandLine.Help.ColorScheme)
use the ProblemCode-based constructor insteaduse the ProblemCode-based constructor insteaduse the ProblemCode-based constructor instead
-
Annotation Interface ElementDescription
CommandLine.execute(String...)
,CommandLine.IParameterExceptionHandler
andCommandLine.IExecutionExceptionHandler