[ 
https://issues.apache.org/jira/browse/MNG-8331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Maarten Mulders updated MNG-8331:
---------------------------------
    Summary: Versioned dependencies may disappear in modelVersion 4.1.0  (was: 
Sometimes versioned dependencies disappear in modelVersion 4.1.0)

> Versioned dependencies may disappear in modelVersion 4.1.0
> ----------------------------------------------------------
>
>                 Key: MNG-8331
>                 URL: https://issues.apache.org/jira/browse/MNG-8331
>             Project: Maven
>          Issue Type: Bug
>          Components: Core
>         Environment: Apache Maven 4.0.0-beta-5
>            Reporter: Maarten Mulders
>            Assignee: Tamas Cservenak
>            Priority: Blocker
>             Fix For: 4.0.0-beta-5
>
>
> 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:
> # dependencies that are managed through a BOM.
> # 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.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to