I wonder how much of this will break what we do with the tiles-maven-plugin, where we essentially “inject” parents into the model via a maven extension.
I remember I was seeing some odd issues under earlier builds of 4.x as well some time ago but will need to refresh my memory on what that was now. Something about properties no longer passing down to those injected parents if I recall. Mark -- "Great artists are extremely selfish and arrogant things" — Steven Wilson, Porcupine Tree On 29/03/2022 at 6:30:24 AM, Guillaume Nodet <[email protected]> wrote: > What I have in mind is that plugins that use the new api would receive the > immutable model, while plugins that use the old (3.x) api would receive a > model that would wrap the immutable one. However, I think mutating the > model or the maven project should be done via services provided by the > maven api. That will allow controlling concurrent access, interception, > logging, etc... > For example, adding a source directory in the new api is done using the > ProjectManager, which I think should be the place where the project is > mutated: >
