[
https://issues.apache.org/jira/browse/MNG-6330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16314922#comment-16314922
]
Hudson commented on MNG-6330:
-----------------------------
Build succeeded in Jenkins: Maven TLP (wip) » maven »
MNG-6308_display_packaging #14
See
https://builds.apache.org/job/maven-wip/job/maven/job/MNG-6308_display_packaging/14/
> [regression] Parents relativePath not verified anymore
> ------------------------------------------------------
>
> Key: MNG-6330
> URL: https://issues.apache.org/jira/browse/MNG-6330
> Project: Maven
> Issue Type: Bug
> Components: Bootstrap & Build, Inheritance and Interpolation,
> Reactor and workspace
> Affects Versions: 3.5.0, 3.5.2
> Reporter: Robert Scholte
> Assignee: Robert Scholte
> Priority: Critical
> Fix For: 3.5.3
>
>
> Since Maven 3.0 the relative path of a parent was always verified, an invalid
> value or missing caches parent made the project fail.
> This stopped after 3.5.0, and after a bisect I discovered the behavior
> changed with:
> {noformat}
> cfb075ac706b25df630f3671f61f8d8313e0f138 is the first bad commit
> commit cfb075ac706b25df630f3671f61f8d8313e0f138
> Author: Karl Heinz Marbaise <khmarba...@apache.org>
> Date: Tue May 31 21:39:31 2016 +0200
> [MNG-6030] ReactorModelCache do not used effectively after maven version
> 3.0.5 which cause a large memory footprint
> o Reintroduced ReactorModelCache reduces the memory footprint.
> {noformat}
> It looks like the caching introduced an unwanted behavior of Maven. We must
> decide if we want the relative path to be strict again.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
