[MNG-8331] Versioned dependencies may disappear in modelVersion 4.1.0

• Type: Bug
• Status: Closed
• Priority: Blocker
• Resolution: Fixed
• Fix Version/s: 4.0.0-beta-5
• Component/s: Core
• Environment: Apache Maven 4.0.0-beta-5
• Assignee: Tamas Cservenak
• Reporter: Maarten Mulders
• Created: 18/Oct/24 18:03
• Updated: 19/Oct/24 18:50
• Resolved: 19/Oct/24 18:04

Description

First observations, will elaborate as we discover more.

When using modelVersion 4.1.0, it is possible to declare dependencies without the version element in two scenarios:

1. dependencies that are managed through a BOM.
2. dependencies that live in the same aggregator project.

When you mix dependencies with a version element and dependencies without a version element, the ones with a version element will not be present in the model.

• Only version-less dependencies: works.
• Only versioned dependencies: works.
• Version-less and versioned dependencies mixed: versioned dependencies can disappear, depending on how the version of the version-less dependency would be calculated. It would only disappear when it was calculated from the aggregator project.

This only breaks in modelVersion 4.1.0. Working on an IT that demonstrates this and a fix.

Issue Links

• links to: GitHub Pull Request #393
• links to: GitHub Pull Request #1821
• links to: GitHub Pull Request #1822
• links to: GitHub Pull Request #1823