LogoLogo
diffblue.comFree trial
  • Discover Diffblue Cover
  • Get Started
    • What is Diffblue Cover?
    • Get started
      • Free trial
      • Get started - Cover Plugin
      • Get started - Cover CLI
      • Get started - Cover Pipeline
      • Get started - Cover Reports
    • Specs & Reqs
    • Reference Deployments
    • Licensing
      • Online license activation
      • Offline license activation
      • Diffblue License Manager
    • Update Cover
    • FAQs
    • Diffblue Learning
      • Get started
        • Just the basics
        • Free trial
        • Cover Plugin (IDE)
        • Cover CLI (Command Line)
      • Developer
        • Unit tests (IDE)
        • Unit tests (CLI)
        • Test coverage
      • DevOps
        • GitHub
        • GitLab
        • Other CI
      • Administrator
        • Admin - IntelliJ
        • Admin - CLI
        • Admin - Reports
      • Test coverage
        • Developer
        • Senior developer
        • Cover Reports Administrator
  • EVALUATION & ONBOARDING
    • Proof of Value
    • Jumpstart
      • Prerequisites for onboarding
      • Phase 1: Up and running
        • Module 1: Create your Cover unit test baseline
        • Module 2: Cover Pipeline CI integration
      • Phase 2: Developer productivity
        • Module 3: Getting started using Cover
        • Module 4: Introduction to Cover Reports
      • Phase 3: Advanced topics
        • Module 5: Speed up your test execution
        • Module 6: Getting more from Cover
  • Features
    • Cover Plugin
      • Writing tests
        • Gutter icons
        • Menu options
        • Run configurations
        • Cover Plugin tool window
        • Test Review
        • Test examples
        • Creating partial tests
        • Creating skeleton tests
        • Covering all enum values
        • Test insertion order
        • Diffblue Sandbox
        • Environment Check Cache
      • Project configuration
        • General dependencies
        • Test framework dependencies
      • Cover Plugin settings
        • Test Naming
        • Test Formatting
        • Spring configuration options
        • Method Annotations
        • Test Directory
        • Reset Cover Plugin settings
      • Cover Plugin admin
        • Core Maintenance
        • Cover Plugin toolbar menu
        • Cover Plugin status bar widget
        • Telemetry
        • Memory management
        • Using SonarQube with Cover Plugin
        • Log files
        • Troubleshooting
    • Cover CLI
      • Writing tests
        • Command summary
        • Test examples
        • Creating partial tests
        • Customizing test inputs
        • Customizing test setup
        • Test naming
        • Test formatting
        • Test insertion order
        • Patch files
        • Diffblue Sandbox
        • Operational behaviors
        • Test validation
      • Project configuration
        • Preflight checks
        • General dependencies
        • Test framework dependencies
        • Compiling your project successfully
          • Building a Maven project
          • Building a Gradle project
        • Configuring Cover to work with your project's build system
          • Quick guide
          • Configuration file in detail
          • Getting Started with Ant Projects
          • Default configuration
        • Mocking using Mockito
        • Spring profiles
        • Runtime environment
      • Commands & Arguments
        • Environment configuration for CI
        • Packages, classes, and methods
        • Quoting command line arguments
        • Argument files
      • Cover CLI admin
        • Core Maintenance
        • Telemetry
        • Memory management
        • Using Cover CLI in Eclipse
        • Using SonarQube with Cover CLI
        • Log files
        • Troubleshooting
      • Environment Configuration
    • Cover Pipeline
      • Cover Pipeline for CI
        • Quick Start - General
        • Quick Start - Jenkins
        • Quick Start - Azure Pipelines
        • Quick Start - AWS Codebuild
        • Integrating Diffblue Cover into CI on pull requests
        • Installation - VMs or CI run
      • Cover Pipeline for GitLab
        • Introduction
        • Installation and initial setup
        • GitLab workflow
        • Configuration
        • Troubleshooting
        • Related topics
      • Cover Pipeline for GitHub
        • Introduction
        • Installation and initial setup
        • GitHub workflow
        • Configuration
        • Troubleshooting
        • Related topics
    • Cover Reports
      • Cover Reports Contributor
        • Java project config (JaCoCo)
        • Generate and upload reports bundles
        • Authenticated uploads
      • Cover Reports User
        • Navigation
        • Dashboards
        • Telemetry data
        • Export API
        • Considerations
      • Cover Reports Administrator
        • Install and update Cover Reports
        • Configuration options
        • Database backup
        • SSO with Cover Reports
        • Uninstall Cover Reports
    • Cover Optimize
      • Get started - Cover Optimize
      • Cover Optimize & Gradle
      • Cover Optimize & Maven
      • Patch files
    • Cover Refactor
      • Get started - Cover Refactor
    • Cover Annotations
      • Mocking Annotations
      • Custom Input Annotations
      • Interesting Value Annotations
    • Output Codes
      • E - Environment Codes
      • L - License Codes
      • R - Reason Codes
      • T - Testability Codes
      • V - Validation Codes
      • Working with output codes
        • Working with code E020
        • Working with codes E057 to E065
        • Working with code E085
        • Working with code R005
        • Working with code R006
        • Working with code R008
        • Working with code R011
        • Working with code R012
        • Working with code R013
        • Working with code R026
        • Working with code R031
        • Working with code V003
    • Tutorials
      • How to measure test quality
      • How to improve code coverage
      • How to test a new feature
      • How to find regressions
      • How to use Diffblue Cover in test driven development (TDD)
      • How to write tests for Kotlin projects
      • Examples of tests created by Diffblue Cover
      • Best practices for testing private methods
  • Updates & Upgrades
    • Update Cover
    • Cover Editions
    • What's new
    • Release archive
      • 2025-05-01
      • 2025-04-02
      • 2025-04-01
      • 2025-03-02
      • 2025-03-01
      • 2025-02-02
      • 2025-02-01
      • 2025-01-02
      • 2025-01-01
      • 2024-12-02
      • 2024-12-01
      • 2024-11-02
      • 2024-11-01
      • 2024-10-02
      • 2024-10-01
      • 2024-09-02
      • 2024-09-01
      • 2024-08-02
      • 2024-08-01
      • 2024-07-04
      • 2024-07-03
      • 2024-07-01
      • 2024-06-02
      • 2024-06-01
      • 2024-05-02
      • 2024-05-01
      • 2024-04-02
      • 2024-04-01
      • 2024-03-02
      • 2024-03-01
      • 2024-02-02
      • 2024-02-01
      • 2024-01-02
      • 2024-01-01
      • 2023-12-02
      • 2023-12-01
      • 2023-11-03
      • 2023-11-02
      • 2023-11-01
      • 2023-10-02
      • 2023-10-01
      • 2023-09-02
      • 2023-09-01
      • 2023-08-02
      • 2023-08-01
      • 2023-07-03
      • 2023-07-02
      • 2023-07-01
      • 2023-06-02
      • 2023-06-01
      • 2023-05-02
      • 2023-05-01
      • 2023-04-02
      • 2023-04-01
      • 2023-03-02
      • 2023-03-01
      • 2023-02-02
      • 2023-02-01
      • 2023-01-02
      • 2023-01-01
      • 2022-12-02
      • 2022-12-01
      • 2022-11-02
      • 2022-11-01
      • 2022-10-03
      • 2022-10-02
      • 2022-10-01
      • 2022-09-02
      • 2022-09-01
      • 2022-08-05
      • 2022-08-03
      • 2022-08-02
      • 2022-08-01
      • 2022-07-02
      • 2022-07-01
      • 2022-06-02
      • 2022-06-01
      • 2022-05-02
      • 2022-05-01
      • 2022-04-02
      • 2022-04-01
      • 2022-03-02
      • 2022-03-01
      • 2022-02-02
      • 2022-02-01
      • 2022-01-02
      • 2022-01-01
      • 2021-06-02
      • 2021-02-01
  • Legal
    • Diffblue Legal
      • Diffblue End User License Agreement (EULA)
      • Cover Third Party Notices and/or Licenses
      • Privacy Notice
Powered by GitBook
On this page

Was this helpful?

Export as PDF
  1. Features
  2. Cover CLI
  3. Commands & Arguments

Quoting command line arguments

When dealing with command line arguments such as the --classpath option in different operating systems, proper use of quotes ensures that arguments containing special characters, spaces, or symbols are correctly interpreted. There are various special characters that require special care when used in arguments.

  1. Spaces: Paths with spaces need to be quoted or escaped.

  2. Asterisks (*): Must be quoted if intended as a literal; otherwise, they will be interpreted as wildcards.

  3. Commas (,): Rarely cause issues, but in some contexts, quoting them is safer.

  4. Shell Special Characters: Characters like ~, &, |, <, >, etc., should be quoted or escaped to prevent the shell from misinterpreting them.

  5. Dollar Signs ($): Require escaping or quoting, as $ is used for variable interpolation.

Special Characters and Escaping

Each operating system has slightly different conventions for handling arguments with such characters.

1. Spaces

  • macOS/Linux:

    • Wrap the entire string in double quotes or escape spaces with \ .

      --classpath="~/My Project/classes:/path/with spaces/file.jar"
      --classpath=~/My\ Project/classes:/path/with\ spaces/file.jar
  • Windows:

    • Wrap the path in double quotes to handle spaces.

      --classpath="C:\My Files\classes;C:\Program Files\path with spaces\file.jar"

2. Asterisks (*)

  • macOS/Linux:

    • To prevent the shell from expanding the * as a wildcard, use quotes or escape it with \.

      --classpath="/path/with/*wildcards"
      --classpath=/path/with/\*wildcards
  • Windows:

    • As Wildcards: No need for quotes; cmd interprets them as wildcards.

      As Literals: Use double quotes to avoid wildcard interpretation.

      --classpath="C:\path\with\*wildcards"

3. Commas (,)

  • macOS/Linux:

    • Commas don’t need escaping unless used in contexts where they are interpreted by the shell or program. Quotes are safer in those cases.

      --classpath="~/path,with,commas/classes"
  • Windows:

    • Generally, commas are not special in cmd, but wrapping the path in double quotes ensures safety.

      --classpath="C:\path,with,commas\classes;C:\another,path\example.jar"

4. $, &, <, >, ` (Backtick)

  • macOS/Linux:

    • Escape with \ or wrap the argument in single quotes (') to treat them as literals.

      --classpath=/path/with/\$dollar\&symbol\file.jar
      --classpath='/path/with/$dollar&symbolfile.jar'
  • Windows:

    • Escape these characters with the caret (^) or wrap the entire path in double quotes.

      --classpath=C:\path\with^&special\$characters^file.jar
      --classpath="C:\path\with&special\$charactersfile.jar"

5. Tilde (~)

  • macOS/Linux:

    • The tilde is expanded to the user’s home directory. Escape with \ or wrap in quotes to prevent expansion.

      --classpath="\~/MyApp/classes:/path"
  • Windows:

    • The tilde is not expanded as the home directory shortcut in cmd. However, it can be used as part of the path without escaping. For consistency, wrap in quotes if spaces or other special characters are present.

      --classpath="C:\Users\~username\path\classes"

6. Comparison Between macOS/Linux and Windows cmd

  • Below is an example comparing how you would handle --classpath in macOS/Linux vs. Windows cmd.

    • macOS/Linux Example

      --classpath="~/My Files/classes:/path/with\$special\&characters\`file.jar:/path/with/*wildcards"
    • Windows Example

      --classpath="C:\My Files\classes;C:\path\with^&special\$characters^`file.jar;C:\path\with\*wildcards"

Summary of Quoting Rules

Character

Linux/macOS (bash/zsh)

Windows (cmd)

Spaces

Double quotes (") or escape (\)

Double quotes (")

Asterisks (*)

Double quotes or escape (\)

Double quotes for literals

Commas (,)

Optional quotes

Optional quotes

$, &, <, >, `

Double quotes or escape (\)

Double quotes or escape (^)

~

Expands to home directory; quote or escape (\)

No expansion; use quotes for safety

PreviousPackages, classes, and methodsNextArgument files

Last updated 3 months ago

Was this helpful?