[
https://issues.apache.org/jira/browse/MNG-8117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17844571#comment-17844571
]
ASF GitHub Bot commented on MNG-8117:
-------------------------------------
cstamas commented on code in PR #1502:
URL: https://github.com/apache/maven/pull/1502#discussion_r1593510428
##########
maven-core/src/main/java/org/apache/maven/plugin/version/internal/DefaultPluginVersionResolver.java:
##########
@@ -261,8 +291,12 @@ private boolean isCompatible(PluginVersionRequest request,
String version) {
try {
pluginManager.checkPrerequisites(pluginDescriptor);
- } catch (Exception e) {
- logger.warn("Ignoring incompatible plugin version {}", version, e);
+ } catch (PluginIncompatibleException e) {
+ if (logger.isDebugEnabled()) {
+ logger.warn("Ignoring incompatible plugin version {}: {}",
version, e.getMessage(), e);
Review Comment:
Agreed, all I wanted to distinguish is "with stack trace" or "without stack
trace".
> Improve prerequisite evaluation and plugin version selection logging
> --------------------------------------------------------------------
>
> Key: MNG-8117
> URL: https://issues.apache.org/jira/browse/MNG-8117
> Project: Maven
> Issue Type: Improvement
> Components: Plugins and Lifecycle
> Reporter: Tamas Cservenak
> Priority: Major
> Fix For: 4.0.0, 4.0.0-beta-1
>
>
> Currently, when user uses {{G:A}} the plugin tried is {{G:A:LATEST}} and is
> checked for "compatibility" (Maven prerequisite in Maven3 and Maven4, plus
> for Java prerequisite in Maven4 only). This may lead that "latest" (by Maven
> Metadata) version is not compatible, and Maven will cycle toward older
> versions. But the console output is a mess.
> Current output can be seen in this gist:
> [https://gist.github.com/cstamas/e44a2e51f5ec9f2e803dfb1d487d2fd5]
> PR creates output like this:
> https://gist.github.com/cstamas/3ca4bc6cea5f701054061871b5db3f35
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
