Issue ID: BACK-1 Status: ✅ RESOLVED Date: October 7, 2025
The Maven proxy issue has been permanently fixed by creating project-level Maven configuration files that bypass the system-wide ~/.m2/settings.xml completely.
File: backend/.mvn/settings.xml
File: backend/.mvn/maven.config
~/.m2/settings.xmlFiles: backend/mvnw, backend/mvnw.cmd
cd backend
# Build the project (recommended)
./mvnw clean install
# Run tests
./mvnw test
# Package for deployment
./mvnw clean package
No setup required! Works immediately on any machine.
cd backend
./mvnw clean compile
Result:
https://repo.maven.apache.org/maven2 (Maven Central)| Before | After | |--------|-------| | ❌ Blocked by proxy | ✅ Direct connection | | ❌ Manual setup needed | ✅ Zero configuration | | ❌ Build failures | ✅ Builds successfully | | ⚠️ Inconsistent across machines | ✅ Identical everywhere |
backend/
├── .mvn/
│ ├── maven.config # NEW - Forces project settings
│ ├── settings.xml # NEW - No proxy config
│ └── wrapper/ # NEW - Maven wrapper files
├── mvnw # NEW - Maven wrapper (Unix)
└── mvnw.cmd # NEW - Maven wrapper (Windows)
See: backend/MAVEN_PROXY_RESOLVED.md
BACK-1: ✅ RESOLVED - No longer blocking Sprint 1
Status: 🟢 PRODUCTION READY
All team members can now build the backend without proxy issues!
Reacties