Unfortunately, I already tried it but v3.3.1 of the maven-common-artifact-filters is for the moment in no maven repository available, so dependency resolution fails. I don't know where to download the artifact otherwise (github page doesn't include references to builds).
Kind Regards, J.P. -----Original Message----- From: Karl Heinz Marbaise <khmarba...@gmx.de> Sent: dinsdag 19 juli 2022 13:42 To: Maven Users List <users@maven.apache.org> Subject: Re: Maven-Assembly-Plugin v3.4.1 not correctly processing assembly descriptors? Hi, You can verify that if you simply add the maven-common-artifact-filters version in the dependencies part of the plugin configuration where you defined the <groupId>dvtm.base</groupId> <artifactId>Assembly</artifactId> Kind regards Karl Heinz Marbaise On 19.07.22 12:55, Jean Pierre URKENS wrote: > Looks like the issue is already reported: > https://issues.apache.org/jira/projects/MASSEMBLY/issues/MASSEMBLY-969 > ?filter=allopenissues > and solved by > https://github.com/apache/maven-common-artifact-filters/pull/29. > > Maven-Assembly-Plugin v3.4.1 uses maven-common-artifact-filters v3.3.0 > -> fails Maven-Assembly-Plugin v3.3.0 uses > maven-common-artifact-filters v3.1.0 -> works > > I will need maven-common-artifact-filters v3.3.1 released on 16/07/2022. > > > > -----Original Message----- > From: Karl Heinz Marbaise <khmarba...@gmx.de> > Sent: dinsdag 19 juli 2022 12:39 > To: Maven Users List <users@maven.apache.org> > Subject: Re: Maven-Assembly-Plugin v3.4.1 not correctly processing > assembly descriptors? > > Hi, > > > can you make an example project on github or alike... > > > Kind regards > Karl Heinz Marbaise > > On 19.07.22 12:07, Jean Pierre URKENS wrote: >> I am trying to re-zip some deliverables into one packaging using the >> maven-assembly-plugin. >> >> My plugin configuration looks like: >> >> <plugin> >> >> <groupId>org.apache.maven.plugins</groupId> >> >> >> <artifactId>*maven-assembly-plugin*</artifactId> >> >> <version>3.4.1</version> >> >> <dependencies> >> >> <dependency> >> >> <groupId>dvtm.base</groupId> >> >> <artifactId>Assembly</artifactId> >> >> >> <version>${dvtm.base.assembly.version}</ >> version> >> >> </dependency> >> >> </dependencies> >> >> <configuration> >> >> <descriptorRefs> >> >> >> <descriptorRef>unziprezip</descriptorRef> >> >> </descriptorRefs> >> >> </configuration> >> >> </plugin> >> >> >> >> I.e. the descriptor unziprezip is located in the artifact >> dvtm.base.Assembly and contains a dependencySet as follows: >> >> <dependencySets> >> >> <dependencySet> >> >> <scope>provided</scope> >> >> <outputDirectory>/</outputDirectory> >> >> <useProjectArtifact>false</useProjectArtifact> >> >> <unpack>true</unpack> >> >> <includes> >> >> *<!-- include pattern is: >> groupId:artifactId:type:classifier -->* >> >> <include>dvtm*:*:zip:deliverables</include> >> >> </includes> >> >> </dependencySet> >> >> </dependencySets> >> >> >> >> Now if I try to execute ‘mvn assembly:single’ I get the error: Error >> creating assembly archive deliverables: archive cannot be empty -> >> [Help 1] >> >> >> >> Looking at the maven log file I see that: >> >> 0.The plugin configuration looks like: >> >> [DEBUG] Configuring mojo >> 'org.apache.maven.plugins:maven-assembly-plugin:3.4.1:single' with >> basic configurator --> >> >> [DEBUG] (s) appendAssemblyId = true >> >> [DEBUG] (f) attach = true >> >> [DEBUG] (s) basedir = >> f:\Documents\Workspaces\AEO-Gitlab\aeo-kmo-portefeuille-parent >> >> [DEBUG] (s) descriptorRefs = [unziprezip] >> >> [DEBUG] (f) dryRun = false >> >> [DEBUG] (f) encoding = UTF-8 >> >> [DEBUG] (s) finalName = AEO-KMO-Portefeuille-Parent-6.0.0-SNAPSHOT >> >> [DEBUG] (f) ignoreDirFormatExtensions = true >> >> [DEBUG] (f) ignoreMissingDescriptor = false >> >> [DEBUG] (f) ignorePermissions = false >> >> [DEBUG] (f) includeProjectBuildFilters = true >> >> [DEBUG] (s) localRepository = id: local >> >> [DEBUG] (f) mavenSession = >> org.apache.maven.execution.MavenSession@586cc15d >> >> [DEBUG] (s) outputDirectory = >> f:\Documents\Workspaces\AEO-Gitlab\aeo-kmo-portefeuille-parent\target >> >> [DEBUG] (f) project = MavenProject: >> dvtm.aeo.kmop:AEO-KMO-Portefeuille-Parent:6.0.0-SNAPSHOT @ >> f:\Documents\Workspaces\AEO-Gitlab\aeo-kmo-portefeuille-parent\pom.xm >> l >> >> [DEBUG] (s) reactorProjects = [MavenProject: >> dvtm.aeo.kmop:AEO-KMO-Portefeuille-Parent:6.0.0-SNAPSHOT @ >> f:\Documents\Workspaces\AEO-Gitlab\aeo-kmo-portefeuille-parent\pom.xm >> l >> ] >> >> [DEBUG] (f) recompressZippedFiles = true >> >> [DEBUG] (f) remoteRepositories = […] >> >> [DEBUG] (f) runOnlyAtExecutionRoot = false >> >> [DEBUG] (s) siteDirectory = >> f:\Documents\Workspaces\AEO-Gitlab\aeo-kmo-portefeuille-parent\target >> \ >> site >> >> [DEBUG] (f) skipAssembly = false >> >> [DEBUG] (s) tarLongFileMode = warn >> >> [DEBUG] (s) tempRoot = >> f:\Documents\Workspaces\AEO-Gitlab\aeo-kmo-portefeuille-parent\target >> \ >> archive-tmp >> >> [DEBUG] (f) updateOnly = false >> >> [DEBUG] (f) useJvmChmod = false >> >> [DEBUG] (s) workDirectory = >> f:\Documents\Workspaces\AEO-Gitlab\aeo-kmo-portefeuille-parent\target >> \ >> assembly\work >> >> [DEBUG] -- end configuration -- >> >> 1.My project dependencies are included (and they do exist): >> >> [DEBUG] Dependencies for project: >> dvtm.aeo.kmop:AEO-KMO-Portefeuille-Parent:jar:6.0.0-SNAPSHOT are: >> >> dvtm.aeo.kmop:AEO-KMO-Portefeuille:zip:deliverables:6.0.0:provided >> >> dvtm.aeo.kmop:AEO-KMO-Portefeuille-EAWS-webservice:zip:deliverables:2. >> 0.2:provided >> >> dvtm.aeo.kmop:AEO-KMO-Portefeuille-Emittent:zip:deliverables:4.0.0:pr >> o >> vided >> >> … >> >> 2.All my dependencies are filtered out when processing the dependencySet: >> >> [DEBUG] Processing DependencySet (output=/) >> >> [DEBUG] Filtering dependency artifacts WITHOUT transitive dependency >> path information. >> >> [DEBUG] dvtm.aeo.kmop:AEO-KMO-Portefeuille:zip:deliverables:6.0.0 >> *was removed by one or more filters*. >> >> … >> >> 3.In the end nothing is included in my assembly hence the final error >> ‘archive cannot be empty’ >> >> >> >> My project dependencies (see point 1) do match with the >> <include>-filter of my dependencySet. >> >> Referring to >> https://maven.apache.org/plugins/maven-assembly-plugin/advanced-descr >> i ptor-topics.html , I do not understand why my dependencies are are >> filtered out? >> >> Is there a reference manual describing the exact configuration of the >> maven element <dependencySet>? >> >> >> >> *NOTE:* with maven-assembly-plugin set to version 3.3.0 the archive >> is correctly assembled. >> >> >> >> Regards, >> >> >> >> J.P. >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > Mit freundlichem Gruß Karl Heinz Marbaise -- SoftwareEntwicklung Beratung Schulung Tel.: +49 (0) 2405 / 415 893 Dipl.Ing.(FH) Karl Heinz Marbaise USt.IdNr: DE191347579 Hauptstrasse 177 52146 Würselen https://www.soebes.de --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
