[
https://issues.apache.org/jira/browse/MNG-8646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guillaume Nodet updated MNG-8646:
---------------------------------
Description:
Several "grey areas" in here:
* model request type CONSUMER_PARENT is used for non-locally built projects
(ie. plugins invoked with direct mojo invocation), this seems strange
* remote repositories are injected ONLY when injecting lifecycle plugins
(processPlugins=true). This was ok when root pom was defining default
repository, but that's not the case anymore, and this results in projects built
that has 0 remote reposes.
was:
Several "grey areas" in here:
* model request type CONSUMER_PARENT is used for non-locally built projects
(ie. plugins invoked with direct mojo invocation), this seems strange
* remote repositories are injected ONLY when injecting lifecycle plugins
(processPlugins=true). This was ok when reposes were inherited, but they are
not inherited anymore, and this results in projects built that has 0 remote
reposes.
> org.apache.maven.project.DefaultProjectBuilder issues
> -----------------------------------------------------
>
> Key: MNG-8646
> URL: https://issues.apache.org/jira/browse/MNG-8646
> Project: Maven
> Issue Type: Bug
> Components: Core
> Reporter: Tamas Cservenak
> Priority: Major
> Fix For: 4.0.0-rc-4
>
>
> Several "grey areas" in here:
> * model request type CONSUMER_PARENT is used for non-locally built projects
> (ie. plugins invoked with direct mojo invocation), this seems strange
> * remote repositories are injected ONLY when injecting lifecycle plugins
> (processPlugins=true). This was ok when root pom was defining default
> repository, but that's not the case anymore, and this results in projects
> built that has 0 remote reposes.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
