CLI Standardization Examples (Before vs After)
This section demonstrates how legacy, technology-specific CLI parameters map to the new standardized naming convention.
Java
java -jar sl-build-scanner.jar config \
--token <token> \
--appName my-app \
--branchName release/1.0 \
--buildName build-123 \
--includePackages com.myapp.* \
--excludePackages com.myapp.test.*
java -jar sl-build-scanner.jar scan \
--token <token> \
--buildSessionIdFile buildSessionId.txt \
--scanDir ./target
java -jar sl-build-scanner.jar -config \
-token <token> \
-appname my-app \
-branchname release/1.0 \
-buildname build-123 \
-packagesincluded com.myapp.* \
-packagesexcluded com.myapp.test.*
java -jar sl-build-scanner.jar -scan \
-token <token> \
-buildsessionidfile buildSessionId.txt \
-workspacepath ./target.NET
dotnet ./<agent-path>/SL.DotNet.dll scan \
--token <token> \
--buildSessionIdFile buildSessionId.txt \
--scanDir ./bindotnet ./<agent-path>/SL.DotNet.dll scan \
--token <token> \
--buildSessionIdFile buildSessionId.txt \
--workspacePath ./binNode.js
Python
Go
PreviousConsistent CLI Parameters Naming Across TechnologiesNextStandardized CLI Parameters Migration
Last updated
Was this helpful?

