What it is A Java web application (Maven-based, with both a plain Java app and a Servlet/JSP webapp structure) built, packaged into a WAR/JAR, and containerized for deployment.

What I built

Set up the project structure with Maven (pom.xml, src/main/java, src/main/webapp) — including a servlet-based structure (HelloServlet.java, index.jsp, web.xml) generated in one version, and a standalone Spring Boot app scaffolded via Spring Initializr in another

Ran mvn package to build the application — confirmed a clean BUILD SUCCESS, producing a deployable WAR file

Wrote a Dockerfile to containerize the app on top of a Tomcat base image

Built the Docker image (docker-java-webapp:v1) and verified it locally — confirmed the container was running and mapped to port 8080 (docker ps showing the container Up and healthy)

Tagged and pushed the image to Docker Hub (mnqw1209/java-docker-app:v1) so it could be pulled and deployed from anywhere — including by my separate deployment automation script

Result Verified with docker images and docker ps that the image built correctly and the container ran successfully on the expected port. Pushed all image layers to Docker Hub successfully, confirmed by the registry digest.

Why it matters This is the "build and publish" half of a full CI/CD-style workflow: the app is built once, containerized, and pushed to a registry — after which any server can pull and run it consistently, which is exactly what my [[server automation project]] does on the deployment side. Together they form a complete build → publish → deploy pipeline.

Tech stack Java · Maven · Spring Boot · Docker · Docker Hub · Tomcat