[jira] [Comment Edited] (MNG-5971) Imported dependencies should be available to inheritance processing

["Andy Wilkinson (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/MNG-5971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15152382#comment-15152382 ] 

Andy Wilkinson edited comment on MNG-5971 at 2/18/16 2:41 PM:
--------------------------------------------------------------

{quote}
For the include scope it will not be possible to use anything requiring inheritance processing. Properties would be available only after inheritance processing has been performed.
{quote}

Is that due to a technical restriction or a design choice that's been made? If I can use a property when defining a managed dependency directly, why can't I also use a property when I'm using the new {{include}} scope? Put another way, once property interpolation is available can't the model be processed such that any {{include}}-scoped dependency is replaced with the content of the bom that it references?


was (Author: awilkinson):
> For the include scope it will not be possible to use anything requiring inheritance processing. Properties would be available only after inheritance processing has been performed.

Is that due to a technical restriction or a design choice that's been made? If I can use a property when defining a managed dependency directly, why can't I also use a property when I'm using the new {{include}} scope? Put another way, once property interpolation is available can't the model be processed such that any {{include}}-scoped dependency is replaced with the content of the bom that it references?

> Imported dependencies should be available to inheritance processing
> -------------------------------------------------------------------
>
>                 Key: MNG-5971
>                 URL: https://issues.apache.org/jira/browse/MNG-5971
>             Project: Maven
>          Issue Type: Wish
>          Components: Dependencies
>    Affects Versions: 3.3.3
>            Reporter: Stephane Nicoll
>            Priority: Trivial
>
> When a project extends from a parent with a {{dependencyManagement}} section, it is not always possible to properly override (and align) the version to use for a group of dependencies.
> We typically use Bill Of Materials to gather a group of modules and make sure their versions are consistent. 
> The following project demonstrates the issue: https://github.com/snicoll-scratches/maven-dependency-management
> The first commit is a working use case where the parent uses a bom with version A and we use the same bom with version B in the child. Version B is used as expected.
> The second commit demonstrates the faulty scenario. Rather than using a bom in the parent, we use a direct dependency (provided by that bom). We still use the bom with a different version. In that case all the dependencies but the one provided by the parent are overridden (leading to mixed versions for the dependencies provided by the BOM).
> It looks like the distance is still used to compute the version while the graph of dependencies should be flatten at each step for a proper override. 
> Thoughts? Thanks!



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)