{"id":210,"date":"2026-10-12T21:01:39","date_gmt":"2026-10-12T21:01:39","guid":{"rendered":"http:\/\/www.scmgalaxy.com\/tutorials\/2010\/03\/21\/power-point-ppt-using-ant-to-build-j2-ee-application\/"},"modified":"2026-10-12T21:01:39","modified_gmt":"2026-10-12T21:01:39","slug":"power-point-ppt-using-ant-to-build-j2-ee-application","status":"publish","type":"post","link":"https:\/\/www.devopsschool.com\/blog\/power-point-ppt-using-ant-to-build-j2-ee-application\/","title":{"rendered":"Using Apache Ant to Build J2EE Applications: Workflow, build.xml Template, and Commands"},"content":{"rendered":"\n

Apache Ant is a target-driven build tool that is still widely encountered in legacy Java EE (historically called J2EE) environments. This guide is for engineers who need to maintain, troubleshoot, or standardize Ant-based enterprise builds, with a clear workflow, practical commands, and reusable configuration examples.<\/p>\n\n\n\n

Originally published on 2010-03-21; fully revised and updated.<\/em><\/p>\n\n\n\n

Original presentation and attribution<\/h2>\n\n\n\n

The original post was primarily a slide embed. Source links preserved here: original article permalink<\/a>, Using Ant To Build J2 Ee Applications<\/a>, and author profile Rajesh Kumar<\/a>.<\/p>\n\n\n\n

\"Using<\/figure>\n\n\n\n
https:\/\/www.slideshare.net\/rajeshatbuzz\/using-ant-to-build-j2-ee-applications<\/div><\/figure>\n\n\n\n

What Ant typically handles in a J2EE build<\/h2>\n\n\n\n

In enterprise Java projects, Ant usually orchestrates repeatable steps from source code to deployable artifacts. A typical Ant file (build.xml<\/code>) defines targets and dependencies between those targets.<\/p>\n\n\n\n

  • Clean old build outputs<\/li>
  • Compile Java sources with explicit classpaths<\/li>
  • Assemble WAR files for web modules<\/li>
  • Assemble JAR modules (for example, EJB-related classes)<\/li>
  • Package EAR files for application server deployment<\/li>
  • Copy artifacts to a deployment directory or handoff location<\/li><\/ul>\n\n\n\n

    Reference workflow for an Ant-based J2EE pipeline<\/h2>\n\n\n\n

    This is a practical flow you can adapt for CI jobs or local builds.<\/p>\n\n\n\n

    \nflowchart TD\n    A[Developer updates source] --> B[ant clean]\n    B --> C[ant compile]\n    C --> D[ant test]\n    D --> E{Tests pass}\n    E -- no --> F[Fix code and rerun]\n    E -- yes --> G[ant war]\n    G --> H[ant ear]\n    H --> I[Publish artifact to app server]\n<\/pre>\n\n\n\n
    Suggested project layout and properties<\/h2>\n\n\n\n
    Keep paths centralized in build.properties<\/code> so environment changes do not require editing build.xml<\/code>.<\/p>\n\n\n
    inventory-app\/\n\u251c\u2500\u2500 build.xml\n\u251c\u2500\u2500 build.properties\n\u251c\u2500\u2500 lib\/\n\u251c\u2500\u2500 src\/main\/java\/\n\u251c\u2500\u2500 src\/main\/webapp\/\n\u251c\u2500\u2500 src\/main\/config\/META-INF\/application.xml\n\u251c\u2500\u2500 build\/\n\u2514\u2500\u2500 dist\/<\/code><\/span><\/pre>\n\n
    app.name=inventory-app\njava.version=1.8<\/span>\nsrc.dir=src\/main\/java\nweb.dir=src\/main\/webapp\nconf.dir=src\/main\/config\nlib.dir=lib\nbuild.dir=build\nclasses.dir=build\/classes\ndist.dir=dist\ndeploy.dir=\/opt\/<\/span>appserver\/autodeploy<\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
    Example build.xml for compile, WAR, EAR, and deploy<\/h2>\n\n\n\n
    The example below shows a conventional Ant target chain. Adapt module paths and packaging rules to your real application structure.<\/p>\n\n\n
    <project<\/span> name<\/span>='inventory-app'<\/span> default<\/span>='ear'<\/span> basedir<\/span>='.'<\/span>><\/span>\n    <property<\/span> file<\/span>='build.properties'<\/span>\/><\/span>\n\n    <path<\/span> id<\/span>='compile.classpath'<\/span>><\/span>\n        <fileset<\/span> dir<\/span>='${lib.dir}'<\/span>><\/span>\n            <include<\/span> name<\/span>='**\/*.jar'<\/span>\/><\/span>\n        <\/fileset<\/span>><\/span>\n    <\/path<\/span>><\/span>\n\n    <target<\/span> name<\/span>='clean'<\/span>><\/span>\n        <delete<\/span> dir<\/span>='${build.dir}'<\/span>\/><\/span>\n        <delete<\/span> dir<\/span>='${dist.dir}'<\/span>\/><\/span>\n    <\/target<\/span>><\/span>\n\n    <target<\/span> name<\/span>='init'<\/span>><\/span>\n        <mkdir<\/span> dir<\/span>='${classes.dir}'<\/span>\/><\/span>\n        <mkdir<\/span> dir<\/span>='${dist.dir}'<\/span>\/><\/span>\n    <\/target<\/span>><\/span>\n\n    <target<\/span> name<\/span>='compile'<\/span> depends<\/span>='init'<\/span>><\/span>\n        <javac<\/span> srcdir<\/span>='${src.dir}'<\/span>\n               destdir<\/span>='${classes.dir}'<\/span>\n               source<\/span>='${java.version}'<\/span>\n               target<\/span>='${java.version}'<\/span>\n               includeantruntime<\/span>='false'<\/span>\n               classpathref<\/span>='compile.classpath'<\/span>\/><\/span>\n    <\/target<\/span>><\/span>\n\n    <target<\/span> name<\/span>='war'<\/span> depends<\/span>='compile'<\/span>><\/span>\n        <war<\/span> destfile<\/span>='${dist.dir}\/${app.name}.war'<\/span> webxml<\/span>='${web.dir}\/WEB-INF\/web.xml'<\/span>><\/span>\n            <fileset<\/span> dir<\/span>='${web.dir}'<\/span>><\/span>\n                <exclude<\/span> name<\/span>='WEB-INF\/web.xml'<\/span>\/><\/span>\n            <\/fileset<\/span>><\/span>\n            <classes<\/span> dir<\/span>='${classes.dir}'<\/span>\/><\/span>\n            <lib<\/span> dir<\/span>='${lib.dir}'<\/span>\/><\/span>\n        <\/war<\/span>><\/span>\n    <\/target<\/span>><\/span>\n\n    <target<\/span> name<\/span>='ejb-jar'<\/span> depends<\/span>='compile'<\/span>><\/span>\n        <jar<\/span> destfile<\/span>='${dist.dir}\/${app.name}-ejb.jar'<\/span>><\/span>\n            <fileset<\/span> dir<\/span>='${classes.dir}'<\/span>><\/span>\n                <include<\/span> name<\/span>='**\/ejb\/**\/*.class'<\/span>\/><\/span>\n            <\/fileset<\/span>><\/span>\n        <\/jar<\/span>><\/span>\n    <\/target<\/span>><\/span>\n\n    <target<\/span> name<\/span>='ear'<\/span> depends<\/span>='war,ejb-jar'<\/span>><\/span>\n        <ear<\/span> destfile<\/span>='${dist.dir}\/${app.name}.ear'<\/span> appxml<\/span>='${conf.dir}\/META-INF\/application.xml'<\/span>><\/span>\n            <fileset<\/span> dir<\/span>='${dist.dir}'<\/span>><\/span>\n                <include<\/span> name<\/span>='${app.name}.war'<\/span>\/><\/span>\n                <include<\/span> name<\/span>='${app.name}-ejb.jar'<\/span>\/><\/span>\n            <\/fileset<\/span>><\/span>\n        <\/ear<\/span>><\/span>\n    <\/target<\/span>><\/span>\n\n    <target<\/span> name<\/span>='deploy'<\/span> depends<\/span>='ear'<\/span>><\/span>\n        <copy<\/span> file<\/span>='${dist.dir}\/${app.name}.ear'<\/span> todir<\/span>='${deploy.dir}'<\/span> overwrite<\/span>='true'<\/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
    Common Ant commands you can run<\/h2>\n\n\n
    # List available targets<\/span>\nant -p\n\n# Clean and build from scratch<\/span>\nant clean ear\n\n# Build only the web archive<\/span>\nant war\n\n# Deploy to a specific directory at runtime<\/span>\nant deploy -Ddeploy.dir=\/srv\/appserver\/autodeploy<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
    Ant vs Maven vs Gradle in enterprise Java builds<\/h2>\n\n\n\n
    Tool<\/th>Build style<\/th>Dependency management<\/th>Best for<\/th>Typical trade-off<\/th><\/tr><\/thead>
    Ant<\/td>Imperative XML targets and task flow<\/td>Manual classpath or add-ons such as Ivy<\/td>Legacy systems and highly customized build steps<\/td>More boilerplate and convention must be maintained by the team<\/td><\/tr>
    Maven<\/td>Convention-driven lifecycle with POM<\/td>Built-in repository model<\/td>Standardized Java project structure and repeatable enterprise builds<\/td>Less flexible when workflows are unusual<\/td><\/tr>
    Gradle<\/td>Declarative plus programmable DSL<\/td>Built-in repository support<\/td>Large multi-module builds needing flexibility and performance tuning<\/td>Higher DSL complexity for new maintainers<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
    Common pitfalls and best practices<\/h2>\n\n\n\n
    • Keep environment values externalized:<\/strong> use build.properties<\/code> and runtime -D<\/code> overrides for server-specific paths.<\/li>
    • Make targets composable:<\/strong> separate clean<\/code>, compile<\/code>, war<\/code>, ear<\/code>, and deploy<\/code> so CI can call only what it needs.<\/li>
    • Fail early:<\/strong> ensure compile and test targets run before packaging targets in the dependency chain.<\/li>
    • Avoid hidden local dependencies:<\/strong> keep third-party JAR handling explicit and documented.<\/li>
    • Plan gradual modernization:<\/strong> if migration is needed, map current Ant targets to Maven\/Gradle equivalents before changing tooling.<\/li><\/ul>\n\n\n\n
      If your organization still runs Ant for Java EE delivery, consistency matters more than novelty: clear target dependencies, centralized properties, and deterministic packaging will reduce build failures and deployment drift.<\/p>\n","protected":false},"excerpt":{"rendered":"
      A practical, modernized guide to building legacy J2EE\/Java EE applications with Apache Ant. Learn the build workflow, use a reusable build.xml template, and compare Ant with Maven and Gradle.<\/p>\n","protected":false},"author":1,"featured_media":4231,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_joinchat":[],"footnotes":""},"categories":[12],"tags":[209,310,91,3755,3756,3758,3759,3760,1122,3757,3761,1806,3752,3754,3727,3728,593,3753,213],"class_list":["post-210","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-apache-ant","tag-ant","tag-application","tag-build","tag-build-j2ee-application","tag-build-j2ee-application-using-ant","tag-build-j2ee-application-using-ant-ppt","tag-build-j2ee-application-using-ant-presentation","tag-build-j2ee-application-using-ant-slideshare","tag-guide","tag-how-to-build-j2ee-application-in-ant","tag-how-to-build-j2ee-application-in-ant-ppt","tag-instruction","tag-j2ee","tag-j2ee-application","tag-ppt","tag-ppt-presentation","tag-process","tag-slideshare","tag-tutorial"],"_links":{"self":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/210","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=210"}],"version-history":[{"count":4,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/210\/revisions"}],"predecessor-version":[{"id":79043,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/210\/revisions\/79043"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/media\/4231"}],"wp:attachment":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/media?parent=210"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/categories?post=210"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/tags?post=210"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}