When a Spring Boot project is packaged as a jar it runs with the embedded Tomcat using the application's own configuration, while a war package relies on an external Tomcat container, adopts the container's settings such as the default 8080 port, and requires additional Maven configuration and a ServletInitializer class.
This guide shows how to download the Jenkins WAR package, start it with nohup java -jar, resolve common errors, install required Linux fonts and Xvfb, and configure global tools such as Maven, JDK, and Git for a fully functional CI server.
This guide shows how to containerize Java SpringBoot JAR or traditional WAR projects with Docker and Nginx, providing a unified, reproducible deployment pipeline that eliminates environment conflicts, simplifies port management, and enables seamless development‑to‑production transitions.
This article explains why a Spring Boot application runs with the configured port when packaged as a JAR using the embedded Tomcat, but switches to Tomcat's default port and context path when deployed as a WAR, and provides step‑by‑step instructions to package and deploy both formats along with historical context and technical differences.
This article explains the differences between JAR and WAR files, why Spring Boot runs with an embedded Tomcat when packaged as a JAR, how deployment changes when using an external Tomcat, and provides step‑by‑step instructions with Maven configurations to build Spring Boot applications as either JAR or WAR packages.
This article explains the differences between JAR and WAR packaging for Spring Boot applications, shows why embedded Tomcat behaves differently from external Tomcat, and provides step‑by‑step instructions with Maven commands and pom.xml modifications to build both JAR and WAR artifacts.
This article explains why a Spring Boot project runs differently when packaged as a JAR versus a WAR, outlines the historical evolution of Java web containers, compares the characteristics of JAR and WAR files, and provides step‑by‑step Maven commands and pom.xml configurations for building both package types.
This article explains why a Spring Boot application behaves differently when run as a JAR versus deployed as a WAR, outlines the historical context of servlet containers, compares JAR and WAR formats, and provides step‑by‑step Maven commands and pom.xml modifications for packaging both types.
A developer discovers a nearly 2 GB Java WAR file packed with an old JDK and a game, learns how a careless SVN commit caused deployment nightmares, and later confronts poor coding practices and naming conventions that highlight the need for proper environment setup and rigorous code reviews.
Despite relentless Russian attacks, Ukraine's vast community of software engineers continues to deliver code and support both civilian and military efforts, illustrating remarkable resilience and the critical role of remote tech teams in global supply chains.
This guide shows how to change a Spring Boot project’s packaging to WAR, remove the embedded Tomcat, add the servlet‑api dependency, create a servlet initializer, build the WAR with Maven, and deploy it to an external Tomcat server for verification.
This article explains the differences between the WAR and WAR exploded deployment modes in Java web projects, compares their packaging and hot‑deployment capabilities, shows experimental results on path resolution, and provides practical tips for configuring Tomcat for effective development.
This tutorial walks you through using MyEclipse and Ant to generate a WAR file for a Java web project, covering project structure, build.xml configuration, environment setup, common pitfalls, and a complete Ant build script for reliable deployment.
