maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Scholte (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (MNG-6330) [regression] Parents relativePath not verified anymore
Date Fri, 29 Dec 2017 09:51:00 GMT

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

Robert Scholte closed MNG-6330.
-------------------------------
       Resolution: Fixed
         Assignee: Robert Scholte
    Fix Version/s:     (was: 3.5.3-candidate)
                   3.5.3

Fixed in [df5169bdf9fead590d48e23fb182d7f73f1deb3d|http://git-wip-us.apache.org/repos/asf/maven/commit/df5169bd]
Corresponding IT in [1797b9ec156cffbb1bd17e731afea5850bbde1a6|http://git-wip-us.apache.org/repos/asf/maven-integration-testing/commit/1797b9ec]

> [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 <khmarbaise@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)

Mime
View raw message