{"id":220,"date":"2026-10-12T21:11:11","date_gmt":"2026-10-12T21:11:11","guid":{"rendered":"http:\/\/www.scmgalaxy.com\/tutorials\/2010\/03\/21\/power-point-ppt-using-ant-to-build-j2-ee-application-2\/"},"modified":"2026-10-12T21:11:11","modified_gmt":"2026-10-12T21:11:11","slug":"power-point-ppt-using-ant-to-build-j2-ee-application-2","status":"publish","type":"post","link":"https:\/\/www.devopsschool.com\/blog\/power-point-ppt-using-ant-to-build-j2-ee-application-2\/","title":{"rendered":"Using Apache Ant to Build and Package J2EE Applications (WAR\/EAR)"},"content":{"rendered":"\n

Apache Ant is a task-based build tool that can compile Java source code and package web and enterprise archives for J2EE applications (now commonly referred to as Jakarta EE). This guide is for engineers maintaining or modernizing Ant-based projects, and it covers a practical build flow, a reusable build.xml<\/code> pattern, and CI-friendly command usage.<\/p>\n\n\n\n

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

Slide deck reference from the original post<\/h2>\n\n\n\n

The original article was a short embed-only post. The Slideshare shortcode is preserved below for archival continuity.<\/p>\n\n\n\n

{slideshare}[slideshare id=1117755&doc=usinganttobuildj2eeapplications-090308134153-phpapp02]{\/slideshare}<\/p>\n\n\n\n

How the Ant workflow maps to J2EE packaging<\/h2>\n\n\n\n

In a typical Ant-driven Java enterprise build, you clean old artifacts, compile Java classes, assemble a WAR for the web module, then optionally wrap that WAR into an EAR for deployment to an application server.<\/p>\n\n\n\n

\nflowchart LR\n    A[Developer updates source] --> B[Run ant clean]\n    B --> C[Compile Java classes]\n    C --> D[Copy web resources]\n    D --> E[Build WAR file]\n    E --> F[Assemble EAR file]\n    F --> G[Publish artifact]\n    G --> H[Deploy to application server]\n<\/pre>\n\n\n\n
Recommended project layout<\/h2>\n\n\n\n
A predictable directory structure keeps Ant targets easy to read and maintain.<\/p>\n\n\n\n
  • src\/main\/java<\/code> for Java source files<\/li>
  • src\/main\/webapp<\/code> for JSP\/static files and WEB-INF\/web.xml<\/code><\/li>
  • src\/main\/application<\/code> for EAR-level metadata such as META-INF\/application.xml<\/code><\/li>
  • lib<\/code> for third-party JAR dependencies used at compile\/package time<\/li>
  • build<\/code> for intermediate output (classes, temp files)<\/li>
  • dist<\/code> for final deployable artifacts (.war<\/code>, .ear<\/code>)<\/li><\/ul>\n\n\n\n
    Example build.xml for compile, WAR, and EAR targets<\/h2>\n\n\n\n
    This example shows a straightforward target chain: clean<\/code> \u2192 compile<\/code> \u2192 war<\/code> \u2192 ear<\/code>.<\/p>\n\n\n
    <project<\/span> name<\/span>=\"sample-j2ee-app\"<\/span> default<\/span>=\"ear\"<\/span> basedir<\/span>=\".\"<\/span>><\/span>\n    <property<\/span> name<\/span>=\"src.dir\"<\/span> value<\/span>=\"src\/main\/java\"<\/span>\/><\/span>\n    <property<\/span> name<\/span>=\"web.dir\"<\/span> value<\/span>=\"src\/main\/webapp\"<\/span>\/><\/span>\n    <property<\/span> name<\/span>=\"build.dir\"<\/span> value<\/span>=\"build\"<\/span>\/><\/span>\n    <property<\/span> name<\/span>=\"classes.dir\"<\/span> value<\/span>=\"${build.dir}\/classes\"<\/span>\/><\/span>\n    <property<\/span> name<\/span>=\"dist.dir\"<\/span> value<\/span>=\"dist\"<\/span>\/><\/span>\n\n    <path<\/span> id<\/span>=\"compile.classpath\"<\/span>><\/span>\n        <fileset<\/span> dir<\/span>=\"lib\"<\/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> destdir<\/span>=\"${classes.dir}\"<\/span> includeantruntime<\/span>=\"false\"<\/span>><\/span>\n            <classpath<\/span> refid<\/span>=\"compile.classpath\"<\/span>\/><\/span>\n        <\/javac<\/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}\/sample.war\"<\/span> webxml<\/span>=\"${web.dir}\/WEB-INF\/web.xml\"<\/span>><\/span>\n            <fileset<\/span> dir<\/span>=\"${web.dir}\"<\/span>\/><\/span>\n            <classes<\/span> dir<\/span>=\"${classes.dir}\"<\/span>\/><\/span>\n            <lib<\/span> dir<\/span>=\"lib\"<\/span>\/><\/span>\n        <\/war<\/span>><\/span>\n    <\/target<\/span>><\/span>\n\n    <target<\/span> name<\/span>=\"ear\"<\/span> depends<\/span>=\"war\"<\/span>><\/span>\n        <ear<\/span> destfile<\/span>=\"${dist.dir}\/sample.ear\"<\/span> appxml<\/span>=\"src\/main\/application\/META-INF\/application.xml\"<\/span>><\/span>\n            <fileset<\/span> dir<\/span>=\"${dist.dir}\"<\/span>><\/span>\n                <include<\/span> name<\/span>=\"sample.war\"<\/span>\/><\/span>\n            <\/fileset<\/span>><\/span>\n        <\/ear<\/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
    Run common Ant commands<\/h2>\n\n\n\n
    Use explicit targets in local development and CI so the build path is predictable.<\/p>\n\n\n
    ant clean\nant compile\nant war\nant ear\nant -Dbuild.number=20261012 ear<\/code><\/span><\/pre>\n\n\n
    Ant vs Maven vs Gradle at a glance<\/h2>\n\n\n\n
    If you are deciding whether to keep Ant or migrate, compare the build model and operational trade-offs.<\/p>\n\n\n\n
    Tool<\/th>Build definition style<\/th>Dependency handling<\/th>Typical fit<\/th><\/tr><\/thead>
    Ant<\/td>Explicit XML targets and task order<\/td>Manual management or add-on tooling<\/td>Legacy builds needing fine-grained task control<\/td><\/tr>
    Maven<\/td>Convention-based lifecycle (POM)<\/td>Built-in repository-driven model<\/td>Teams preferring standard Java conventions<\/td><\/tr>
    Gradle<\/td>Scripted DSL with tasks and plugins<\/td>Built-in repository-driven model<\/td>Flexible multi-module builds and custom automation<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
    Common pitfalls and best practices<\/h2>\n\n\n\n
    • Keep artifact assembly deterministic: avoid hidden local dependencies outside lib<\/code> or repository config.<\/li>
    • Use clear target dependencies so ant ear<\/code> always implies compile and WAR creation.<\/li>
    • Parameterize environment-specific values with properties files instead of editing build.xml<\/code> per environment.<\/li>
    • Treat dist<\/code> output as immutable deployment artifacts once built.<\/li>
    • Document expected JDK level and app-server requirements alongside the build file.<\/li><\/ul>\n","protected":false},"excerpt":{"rendered":"
      This revised guide explains how to use Apache Ant to compile Java code and package J2EE applications into WAR and EAR artifacts. It includes a practical workflow diagram, a reusable build.xml example, command usage, and a comparison with Maven and Gradle.<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_joinchat":[],"footnotes":""},"categories":[8],"tags":[],"class_list":["post-220","post","type-post","status-publish","format-standard","hentry","category-training"],"_links":{"self":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/220","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=220"}],"version-history":[{"count":1,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/220\/revisions"}],"predecessor-version":[{"id":79044,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/220\/revisions\/79044"}],"wp:attachment":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/media?parent=220"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/categories?post=220"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/tags?post=220"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}