[ https://issues.apache.org/jira/browse/MNG-6530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16708537#comment-16708537 ]
Mickael Istria commented on MNG-6530: ------------------------------------- {quote}Regarding release notes, they are written at the end. I suggest to add a paragraph in the description of this issue which could be added to the release notes.{quote} I was more talking about the 3.6.0 release note to have a note about this bug, so people who upgrade from a Maven version to another (who should read the release notes of all versions before doing so) would receive a warning and not adopt 3.6.x if they are using ProjectBuilder in a context where files can change. Also, I'd like some confirmation here: If I add a field in ProjectBuildingRequest instead of the system property, would this be merged? I can spend time to work on those things, but I need some guidance to not waste time in undesired changes. > Regression in ProjectBuilder when file change between invocations (introduced > by MNG-6311) > ------------------------------------------------------------------------------------------ > > Key: MNG-6530 > URL: https://issues.apache.org/jira/browse/MNG-6530 > Project: Maven > Issue Type: Bug > Components: core > Affects Versions: 3.6.0 > Reporter: Mickael Istria > Priority: Critical > Fix For: 3.6.1 > > > The patch for MNG-6311 introduces a regression in ProjectBuilder due to > missing cache invalidation when content change. > It was identified as a potential issue by [~fbricon] on Oct 10, yet no > further investigation happened and Maven 3.6.0 was released with this > regression. > This regression prevents Eclipse m2e (and probably most APIs using the > ProjectBuilder for a longer session which allows pom.xml files to be > modified) from adopting 3.6.0. -- This message was sent by Atlassian JIRA (v7.6.3#76005)