{"id":142,"date":"2026-10-12T12:51:54","date_gmt":"2026-10-12T12:51:54","guid":{"rendered":"http:\/\/www.scmgalaxy.com\/tutorials\/2009\/06\/20\/access-all-java-system-properties-directly\/"},"modified":"2026-10-12T12:51:54","modified_gmt":"2026-10-12T12:51:54","slug":"access-all-java-system-properties-directly","status":"publish","type":"post","link":"https:\/\/www.devopsschool.com\/blog\/access-all-java-system-properties-directly\/","title":{"rendered":"Apache Ant Properties: Access Java System Properties, Environment Variables, and Runtime Inputs"},"content":{"rendered":"\n

Originally published on 2009-06-20; fully revised and updated.<\/em><\/p>\n\n\n\n

If you use Apache Ant, property expansion via ${name}<\/strong> is the core mechanism for build-time configuration. This guide shows how to read Java system properties directly, import environment variables, pass values with -D<\/strong>, and use interactive input only where it makes sense.<\/p>\n\n\n\n

This revised article expands the original quick tip from DevOpsSchool<\/a> into a practical reference.<\/p>\n\n\n\n

\"Java<\/figure>\n\n\n\n

Property sources in Ant at a glance<\/h2>\n\n\n\n

In Ant build files, you reference a property as ${property.name}<\/strong>. Values can come from multiple sources during a build run.<\/p>\n\n\n\n

Source<\/th>Reference style<\/th>How it is set<\/th>Typical use<\/th><\/tr><\/thead>
Java system property<\/td>${user.home}<\/code><\/td>Provided by the JVM running Ant<\/td>Runtime and host metadata<\/td><\/tr>
Environment variable<\/td>${env.PATH}<\/code><\/td>Imported with the Ant property task using an environment<\/code> prefix<\/td>OS-level paths and machine config<\/td><\/tr>
Command-line property<\/td>${deploy.env}<\/code><\/td>ant -Ddeploy.env=prod<\/code><\/td>CI\/CD and per-run overrides<\/td><\/tr>
Interactive input<\/td>${release.version}<\/code><\/td>Set with Ant input<\/code> task<\/td>Local\/manual runs<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

Read Java system properties directly<\/h2>\n\n\n\n

You can use common JVM properties directly in your build file without extra setup.<\/p>\n\n\n\n

  • ${user.name}<\/code><\/li>
  • ${user.dir}<\/code><\/li>
  • ${user.home}<\/code><\/li>
  • ${java.version}<\/code><\/li><\/ul>\n\n\n
    <project<\/span> name<\/span>='sys-props-demo'<\/span> default<\/span>='show-system-props'<\/span>><\/span>\n    <target<\/span> name<\/span>='show-system-props'<\/span>><\/span>\n        <echo<\/span> message<\/span>='user.name = ${user.name}'<\/span>\/><\/span>\n        <echo<\/span> message<\/span>='user.dir  = ${user.dir}'<\/span>\/><\/span>\n        <echo<\/span> message<\/span>='user.home = ${user.home}'<\/span>\/><\/span>\n        <echo<\/span> message<\/span>='java.version = ${java.version}'<\/span>\/><\/span>\n    <\/target<\/span>><\/span>\n<\/project<\/span>><\/span><\/code><\/span>Code language:<\/span> HTML, XML<\/span> (<\/span>xml<\/span>)<\/span><\/small><\/pre>\n\n\n
    Import environment variables with a prefix<\/h2>\n\n\n\n
    To expose OS environment variables in Ant properties, use the property<\/code> task with an environment prefix (for example, env<\/code>). Then reference values as ${env.VARIABLE_NAME}<\/code>.<\/p>\n\n\n
    <project<\/span> name<\/span>='env-demo'<\/span> default<\/span>='show-env'<\/span>><\/span>\n    <target<\/span> name<\/span>='show-env'<\/span>><\/span>\n        <property<\/span> environment<\/span>='env'<\/span>\/><\/span>\n        <echo<\/span> message<\/span>='PATH = ${env.PATH}'<\/span>\/><\/span>\n        <echo<\/span> message<\/span>='HOME = ${env.HOME}'<\/span>\/><\/span>\n        <echo<\/span> message<\/span>='USERPROFILE = ${env.USERPROFILE}'<\/span>\/><\/span>\n    <\/target<\/span>><\/span>\n<\/project<\/span>><\/span><\/code><\/span>Code language:<\/span> HTML, XML<\/span> (<\/span>xml<\/span>)<\/span><\/small><\/pre>\n\n\n
    Pass properties at runtime with -D<\/h2>\n\n\n\n
    For pipeline-friendly builds, pass values at invocation time so you can reuse the same build file across environments.<\/p>\n\n\n
    ant -Ddeploy.env=staging -Dbuild.number=123 package\nant -Ddeploy.env=prod deploy<\/code><\/span><\/pre>\n\n\n
    Inside build.xml<\/code>, consume those runtime values with normal property syntax.<\/p>\n\n\n
    <target<\/span> name<\/span>='package'<\/span>><\/span>\n    <echo<\/span> message<\/span>='Deploy environment: ${deploy.env}'<\/span>\/><\/span>\n    <echo<\/span> message<\/span>='Build number: ${build.number}'<\/span>\/><\/span>\n<\/target<\/span>><\/span><\/code><\/span>Code language:<\/span> HTML, XML<\/span> (<\/span>xml<\/span>)<\/span><\/small><\/pre>\n\n\n
    Prompt for input during local runs<\/h2>\n\n\n\n
    Ant can prompt for ad hoc input. This is useful for local\/manual execution, but usually unsuitable for non-interactive CI jobs.<\/p>\n\n\n
    <target<\/span> name<\/span>='ask-version'<\/span>><\/span>\n    <input<\/span> addproperty<\/span>='release.version'<\/span> message<\/span>='Enter release version'<\/span>\/><\/span>\n    <echo<\/span> message<\/span>='Release version: ${release.version}'<\/span>\/><\/span>\n<\/target<\/span>><\/span><\/code><\/span>Code language:<\/span> HTML, XML<\/span> (<\/span>xml<\/span>)<\/span><\/small><\/pre>\n\n\n
    Property resolution workflow<\/h2>\n\n\n\n
    \nflowchart TD\n    A[Task needs a property] --> B{Set by D argument}\n    B -- yes --> C[Use command line value]\n    B -- no --> D{Set in build or property file}\n    D -- yes --> E[Use first assigned value]\n    D -- no --> F{Available as Java system property}\n    F -- yes --> G[Use system property]\n    F -- no --> H{Imported from env prefix}\n    H -- yes --> I[Use env prefixed value]\n    H -- no --> J[Optional input or fail]\n<\/pre>\n\n\n\n
    Best practices and common pitfalls<\/h2>\n\n\n\n
    • Use -D<\/code> properties for CI\/CD and environment-specific overrides.<\/li>
    • Import environment variables with a clear prefix (for example, env<\/code>) to avoid naming collisions.<\/li>
    • Avoid interactive input<\/code> tasks in automated pipelines.<\/li>
    • Do not echo sensitive values (tokens, passwords, keys) into logs.<\/li>
    • Keep default values in the build file and override only what is needed per run.<\/li><\/ul>\n","protected":false},"excerpt":{"rendered":"
      Apache Ant lets you reference properties with ${name}, including Java system properties, imported environment variables, and command-line values. This guide shows practical syntax, examples, precedence flow, and common pitfalls for reliable builds.<\/p>\n","protected":false},"author":1,"featured_media":4088,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_joinchat":[],"footnotes":""},"categories":[49],"tags":[380,3303,3308,3301,3305,3306,3113,173,3300,3302,3307,3310,3312,3311,3309,593,1073,3304],"class_list":["post-142","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-general","tag-access","tag-access-java-system-properties-directly","tag-command-line-to-access-java-system-properties","tag-directly","tag-environment-properties","tag-get-all-system-properties-in-java","tag-how-to","tag-java","tag-java-system","tag-java-system-properties","tag-java-system-properties-acces-command-line","tag-java-system-properties-access-guide","tag-java-system-properties-access-instructions","tag-java-system-properties-access-reference","tag-java-system-properties-access-tutorial","tag-process","tag-properties","tag-system-properties"],"_links":{"self":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/142","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/comments?post=142"}],"version-history":[{"count":3,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/142\/revisions"}],"predecessor-version":[{"id":78991,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/142\/revisions\/78991"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/media\/4088"}],"wp:attachment":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/media?parent=142"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/categories?post=142"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/tags?post=142"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}