[
https://issues.apache.org/jira/browse/MNG-8670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Oehme updated MNG-8670:
------------------------------
Description:
When using the new multithreaded builde, there are no ProjectSkipped events for
projects that were skipped due to previous errors. There is no reference to
ProjectSkipped anywhere in BuildPlanExecutor. Compare that to the old
LifecycleModuleBuilder, which fires ProjectSkipped when the reactor is halted
or the project is blacklisted.
Our extension relies on these events to get a complete picture of what happened
during a build.
was:
When using the new multithreaded builder and --fail-fast, there are no
ProjectSkipped events for projects that were skipped due to --fail-fast. There
is no reference to ProjectSkipped anywhere in BuildPlanExecutor. Compare that
to the old LifecycleModuleBuilder, which fires ProjectSkipped when the reactor
is halted or the project is blacklisted.
Our extension relies on these events to get a complete picture of what happened
during a build.
> Concurrent executor doesn't fire ProjectSkipped events
> ------------------------------------------------------
>
> Key: MNG-8670
> URL: https://issues.apache.org/jira/browse/MNG-8670
> Project: Maven
> Issue Type: Bug
> Components: Core
> Affects Versions: 4.0.0-rc-3
> Reporter: Stefan Oehme
> Priority: Major
>
> When using the new multithreaded builde, there are no ProjectSkipped events
> for projects that were skipped due to previous errors. There is no reference
> to ProjectSkipped anywhere in BuildPlanExecutor. Compare that to the old
> LifecycleModuleBuilder, which fires ProjectSkipped when the reactor is halted
> or the project is blacklisted.
>
> Our extension relies on these events to get a complete picture of what
> happened during a build.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
