docker build -t maven-3.0.5 . docker run --rm -v "$PWD":/app -w /app maven-3.0.5 mvn clean package | Use it if… | Don’t use it if… | |------------|------------------| | Your company’s CI is frozen in 2014 | You can upgrade to 3.8+ | | You’re maintaining a Java 7 app | You need Java 11+ | | You love debugging SSL errors | You value your sanity | 📜 The Cheat Sheet (One-Liner for the Impatient) wget https://archive.apache.org/dist/maven/maven-3/3.0.5/binaries/apache-maven-3.0.5-bin.tar.gz && tar -xzf apache-maven-3.0.5-bin.tar.gz && ./apache-maven-3.0.5/bin/mvn -version Now go forth, time traveler, and build that legacy JAR. Just don’t expect --help to be helpful 😉

Force HTTP in your settings.xml :

Example – Surefire:

FROM openjdk:7-jdk ADD apache-maven-3.0.5-bin.tar.gz /opt ENV MAVEN_HOME /opt/apache-maven-3.0.5 ENV PATH $MAVEN_HOME/bin:$PATH Build & run:

/path/to/apache-maven-3.0.5/bin/mvn clean install This is perfect for isolated legacy builds. Why pollute your host?