[
https://issues.apache.org/jira/browse/MNG-7220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17402416#comment-17402416
]
Falko Modler edited comment on MNG-7220 at 8/20/21, 8:57 PM:
-------------------------------------------------------------
Standard Maven plugins are not tested with a new Maven release before it's
released? That's unfortunate, given all the test coverage that's in those
plugins...
I'm not familiar with the internals of {code}@Execute{code}. Does it spawn a
new Thread? Can you point me to the implementation, [~rfscholte]? Thanks!
was (Author: famod):
Standard Maven plugins are not tested with a new Maven release before it's
released? That's unfortunate, given all the test coverage that's in those
plugins...
I'm not familiar with the internals of {noformat}@Execute{noformat}. Does it
spawn a new Thread? Can you point me to the implementation, [~rfscholte]?
Thanks!
> [REGRESSION] test-classpath incorrectly resolved
> -------------------------------------------------
>
> Key: MNG-7220
> URL: https://issues.apache.org/jira/browse/MNG-7220
> Project: Maven
> Issue Type: Bug
> Affects Versions: 3.8.2
> Reporter: Robert Scholte
> Priority: Critical
> Attachments: 381.log, 382.log
>
>
> The integrationtest of MJAVADOC-259 succeeds with Maven 3.8.1, but fails with
> 3.8.2.
> Git bisect identifies 76d5f0d942f52650d3bdf775b6af42d23d69066b as the first
> bad commit
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
