+1 I just tried maven-shade-plugin master with 4.0.0-alpha-2. I have some tests failing, but not the same: * mshade-123/pom.xml * MSHADE-419_createDependencyReducedPom_multimodule/pom.xml * MSHADE-340_shadedTestJarArtifactAttached/pom.xml
MSHADE-123 failure is caused by the use of an old (incompatible) enforcer plugin. [ERROR] Failed to execute goal org.apache.maven.plugins:maven-enforcer-plugin:1.0:enforce (enforce-maven) on project test: Execution enforce-maven of goal org.apache.maven.plugins:maven-enforcer-plugin:1.0:enforce failed: An API incompatibility was encountered while executing org.apache.maven.plugins:maven-enforcer-plugin:1.0:enforce: java.lang.NoSuchMethodError: 'void org.apache.maven.plugin.PluginParameterExpressionEvaluator.<init>(org.apache.maven.execution.MavenSession, org.apache.maven.plugin.MojoExecution, org.apache.maven.project.path.PathTranslator, org.codehaus.plexus.logging.Logger, org.apache.maven.project.MavenProject, java.util.Properties)' This one has been dropped by https://github.com/apache/maven/commit/d75bea415457b2eba7815bb9c3e9cd4e14b47fce so upgrading to the enforcer plugin 3.0.0 will fix those issues. MSHADE-419 and MSHADE-340 failures are caused by the following exception thrown by the jar mojo Caused by: org.apache.maven.plugin.MojoExecutionException: You have to use a classifier to attach supplemental artifacts to the project instead of replacing them. at org.apache.maven.plugins.jar.AbstractJarMojo.execute (AbstractJarMojo.java:317) It seems the above exception is thrown because the same file has already been attached to the artifact. This needs to be investigated further. Le mer. 26 oct. 2022 à 00:13, Slawomir Jaranowski <s.jaranow...@gmail.com> a écrit : > +1 > > Build by Maven 3 ok. > > Just as a curiosity - build project by Maven 4, some IT tests failed, I did > not investigate it. > > [ERROR] * mshade-123/pom.xml > [ERROR] * finalNameBuild-attached/pom.xml > [ERROR] * MSHADE-340_shadedTestJarArtifactAttached/pom.xml > [ERROR] * finalNameShade-attached/pom.xml > [ERROR] * attached-artifact-type/pom.xml > [ERROR] * finalNameShade/pom.xml > [ERROR] * finalNameBuild/pom.xml > [ERROR] * attach-after-lifecycle-fork/pom.xml > > pt., 21 paź 2022 o 23:00 Guillaume Nodet <gno...@apache.org> napisał(a): > > > Hi, > > > > We solved 7 issues: > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317921&version=12352285 > > > > There are still a couple of issues left in JIRA: > > > > > https://issues.apache.org/jira/issues/?jql=project%20%3D%20MSHADE%20AND%20resolution%20%3D%20Unresolved > > > > Staging repo: > > https://repository.apache.org/content/repositories/maven-1815/ > > > > > https://repository.apache.org/content/repositories/maven-1815/org/apache/maven/plugins/maven-shade-plugin/3.4.1/maven-shade-plugin-3.4.1-source-release.zip > > > > Source release checksum(s): > > maven-shade-plugin-3.4.1-source-release.zip - SHA-512 : > > > > > 677bbb062b442b4b1843bdfdd637398aea6c7e99c9eae3db476b9a90323e38f042384c8639ac12f50ad142e664ddd1e09ed1fe44f3dd5a5843023668660e5b8a > > > > Staging site: > > https://maven.apache.org/plugins-archives/maven-shade-plugin-LATEST/ > > > > Guide to testing staged releases: > > https://maven.apache.org/guides/development/guide-testing-releases.html > > > > Vote open for at least 72 hours. > > > > [ ] +1 > > [ ] +0 > > [ ] -1 > > > > -- > > ------------------------ > > Guillaume Nodet > > > > > -- > Sławomir Jaranowski > -- ------------------------ Guillaume Nodet
