Please follow, comments https://issues.apache.org/jira/browse/MENFORCER-447
pon., 19 gru 2022 o 17:53 Mirko Friedenhagen <mfriedenha...@gmx.de> napisał(a): > Hello, > > we have configured this rule for ages and now when executing enforcer, I > get: > > [INFO] --- enforcer:3.1.0:enforce (default-enforce) @ XXXX --- > [INFO] Adding ignore: module-info > [INFO] Adding ignore: META-INF/versions/*/module-info > [ERROR] Rule 19: org.apache.maven.plugins.enforcer.RequirePluginVersions > failed with message: > Some plugins are missing valid versions or depend on Maven 4.0.0-alpha-3 > defaults: (LATEST RELEASE SNAPSHOT are not allowed) > com.unitedinternet.portal.maven2.plugin:portal-manifest-maven-plugin. The > version currently in use is 3.1.3 via super POM or default lifecycle > bindings > net.oneandone.maven.plugins:bill-of-materials-maven-plugin. The version > currently in use is 3.1 via super POM or default lifecycle bindings > org.codehaus.mojo:buildnumber-maven-plugin. The version currently in use > is 3.0.0 via super POM or default lifecycle bindings > org.apache.maven.plugins:maven-source-plugin. The version currently in use > is 3.2.1 via super POM or default lifecycle bindings > org.apache.maven.plugins:maven-site-plugin. The version currently in use > is 3.12.1 via super POM or default lifecycle bindings > org.apache.maven.plugins:maven-resources-plugin. The version currently in > use is 3.1.0 via super POM or default lifecycle bindings > org.apache.maven.plugins:maven-toolchains-plugin. The version currently in > use is 3.1.0 via super POM or default lifecycle bindings > com.unitedinternet.portal.maven2.plugin:portal-dependency-maven-plugin. > The version currently in use is 4.4.42 via super POM or default lifecycle > bindings > org.apache.maven.plugins:maven-compiler-plugin. The version currently in > use is 3.10.1 via super POM or default lifecycle bindings > org.apache.maven.plugins:maven-surefire-plugin. The version currently in > use is 3.0.0-M7 via super POM or default lifecycle bindings > org.apache.maven.plugins:maven-jar-plugin. The version currently in use is > 3.3.0 via super POM or default lifecycle bindings > org.apache.maven.plugins:maven-clean-plugin. The version currently in use > is 3.2.0 via super POM or default lifecycle bindings > org.apache.maven.plugins:maven-failsafe-plugin. The version currently in > use is 3.0.0-M7 via super POM or default lifecycle bindings > org.apache.maven.plugins:maven-wrapper-plugin. The version currently in > use is 3.1.0 via default lifecycle bindings > org.apache.maven.plugins:maven-dependency-plugin. The version currently in > use is 3.4.0 via super POM or default lifecycle bindings > org.apache.maven.plugins:maven-install-plugin. The version currently in > use is 3.1.0 via super POM or default lifecycle bindings > pl.project13.maven:git-commit-id-plugin. The version currently in use is > 4.9.10 via super POM or default lifecycle bindings > org.apache.maven.plugins:maven-deploy-plugin. The version currently in use > is 3.0.0 via super POM or default lifecycle bindings > net.rumati.maven.plugins:velocity-maven-plugin. The version currently in > use is 0.3.1 via super POM or default lifecycle bindings > org.jacoco:jacoco-maven-plugin. The version currently in use is 0.8.8 via > super POM or default lifecycle bindings > org.cyclonedx:cyclonedx-maven-plugin. The version currently in use is > 2.7.3 via super POM or default lifecycle bindings > org.apache.maven.plugins:maven-enforcer-plugin. The version currently in > use is 3.1.0 via super POM or default lifecycle bindings > Best Practice is to always define plugin versions! > > All of these versions are managed in the company-pom’s pluginManagement > section. But maybe this is a followup error because we overrode the default > lifecycle bindings in a component.xml of an extension ( > https://lists.apache.org/thread/lgvbnw4qq30rbx4osn8qzyy2y9ro4hdy). > > In the extension’s component.xml file we did not specify any versions, but > rely on pluginManagement of the including POM. Works fine with Maven 3.8.6 > but now behaves differently with 4.0.0. > > Best Regards > Mirko > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > > -- Sławomir Jaranowski
