Skip to content

docs: revise INSTALL.md with updated Maven setup #11025

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Jun 16, 2025

Conversation

he1l0world
Copy link
Contributor

Description

This PR updates the Maven installation instructions in INSTALL.md.
While following the setup steps to build CloudStack locally as a new contributor, I found that the provided download link for Maven 3.9.9 is no longer active, and the version itself is not listed on the official Apache Maven distribution site.
I’ve updated the instructions to use Maven 3.9.10, which is the most up-to-date version at the time of writing.

Additionally, I added sudo to the tar and ln commands since those require root permission when extracting to or linking under /usr/local.

This small patch improves the onboarding experience for new developers setting up their environment.

Types of changes

  • Breaking change (fix or feature that would cause existing functionality to change)
  • New feature (non-breaking change which adds functionality)
  • Bug fix (non-breaking change which fixes an issue)
  • Enhancement (improves an existing feature and functionality)
  • Cleanup (Code refactoring and cleanup, that may add test cases)
  • build/CI
  • test (unit or integration test code)

Feature/Enhancement Scale or Bug Severity

Feature/Enhancement Scale

  • Major
  • Minor

Bug Severity

  • BLOCKER
  • Critical
  • Major
  • Minor
  • Trivial

Screenshots (if appropriate):

image

How Has This Been Tested?

I manually tested by following the updated instructions to set up Maven 3.9.10 on a fresh environment.

How did you try to break this feature and the system with this change?

Maven 3.x on official Apache Maven distribution site.

Copy link

codecov bot commented Jun 14, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 16.60%. Comparing base (ea7919b) to head (465b635).
Report is 1 commits behind head on main.

Additional details and impacted files
@@             Coverage Diff              @@
##               main   #11025      +/-   ##
============================================
- Coverage     16.60%   16.60%   -0.01%     
- Complexity    13924    13925       +1     
============================================
  Files          5730     5730              
  Lines        508224   508224              
  Branches      61789    61789              
============================================
- Hits          84388    84387       -1     
  Misses       414401   414401              
- Partials       9435     9436       +1     
Flag Coverage Δ
uitests 3.93% <ø> (ø)
unittests 17.49% <ø> (-0.01%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

Copy link
Collaborator

@bernardodemarco bernardodemarco left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Only docs update, lgtm

@DaanHoogland DaanHoogland force-pushed the doc/maven-version-invalid-fix branch from b1136ac to 465b635 Compare June 16, 2025 07:16
@DaanHoogland DaanHoogland merged commit 6aaaa83 into apache:main Jun 16, 2025
26 checks passed
@he1l0world he1l0world deleted the doc/maven-version-invalid-fix branch June 17, 2025 03:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants