Tamas Cservenak created MNG-7826:
------------------------------------
Summary: Maven Plugin Validation: Jacoco plugin is not reported as
problem
Key: MNG-7826
URL: https://issues.apache.org/jira/browse/MNG-7826
Project: Maven
Issue Type: Bug
Components: Plugins and Lifecycle
Affects Versions: 3.9.3
Reporter: Tamas Cservenak
Maven 3.9.2 regarding jacoco maven plugin 0.8.10 reports this:
{noformat}
[WARNING] * org.jacoco:jacoco-maven-plugin:0.8.10
[WARNING] Declared at location(s):
[WARNING] * com.soebes.smpp:smpp:6.0.4-SNAPSHOT (pom.xml) @ line 484
[WARNING] Used in module(s):
[WARNING] * com.soebes.smpp:smpp:6.0.4-SNAPSHOT (pom.xml)
[WARNING] * com.soebes.smpp:smpp-plugins:6.0.4-SNAPSHOT
(smpp-plugins/pom.xml)
[WARNING] Plugin issue(s):
[WARNING] * Plugin is a Maven 2.x plugin, which will be not supported in
Maven 4.x
[WARNING] * Plugin mixes multiple Maven versions: [3.0, 2.0.2]
[WARNING] * Plugin should declare these Maven artifacts in `provided` scope:
[org.apache.maven:maven-repository-metadata:3.0,
org.apache.maven:maven-artifact:3.0]
[WARNING] * Plugin depends on plexus-container-default, which is EOL
{noformat}
and all these are true: culprit is ancient shared file-management, that the
plugin depends in compile scope, while it brings in
* p-c-d
* maven-plugin-api, maven-artifact-manager etc from mvn 2.0.6
* etc
Maven 3.9.3 does not report anything related to this plugin.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
