maven assembly ignora le dipendenze dei genitori
-
06-07-2019 - |
Domanda
Il mio descrittore di assembly applica le inclusioni e le esclude correttamente quando le dipendenze sono incluse direttamente nel file pom.
Tuttavia, quando inserisco le dipendenze nel file pom principale dell'assembly: l'obiettivo della directory indica che le inclusioni e le esclusioni non sono state attivate.
Sai perché maven-assembly-plugin ignora le dipendenze dei genitori? Come posso ripararlo?
Ecco i descrittori di maven e assembly:
Descrizione dell'assembly:
<assembly>
<id>distribution</id>
<formats>
<format>zip</format>
</formats>
<fileSets>
<fileSet>
<includes>
<include>readme.txt</include>
</includes>
</fileSet>
<fileSet>
<directory>target</directory>
<outputDirectory>/lib</outputDirectory>
<includes>
<include>*.jar</include>
</includes>
</fileSet>
</fileSets>
<dependencySets>
<dependencySet>
<outputDirectory>/lib</outputDirectory>
<unpack>false</unpack>
<scope>runtime</scope>
<excludes>
<exclude>org.tanukisoftware:wrapper:exe:3.3.5</exclude>
</excludes>
</dependencySet>
<dependencySet>
<outputDirectory>/bin</outputDirectory>
<unpack>false</unpack>
<scope>runtime</scope>
<includes>
<include>org.tanukisoftware:wrapper:exe:3.3.5</include>
</includes>
</dependencySet>
</dependencySets>
</assembly>
Definizione del plug-in dell'assembly POM figlio:
<plugin>
<artifactId>maven-assembly-plugin</artifactId>
<configuration>
<ignoreDirFormatExtensions>true</ignoreDirFormatExtensions>
<descriptors>
<descriptor>assembly.xml</descriptor>
</descriptors>
</configuration>
<executions>
<execution>
<id>make-assembly</id>
<phase>package</phase>
<goals>
<goal>directory</goal>
</goals>
</execution>
</executions>
</plugin>
Dipendenze POM principali:
<dependencies>
<dependency>
<groupId>org.tanukisoftware</groupId>
<artifactId>wrapper</artifactId>
<version>3.3.5</version>
<type>dll</type>
<scope>runtime</scope>
</dependency>
<dependency>
<groupId>org.tanukisoftware</groupId>
<artifactId>wrapper</artifactId>
<version>3.3.5</version>
<type>exe</type>
<scope>runtime</scope>
</dependency>
<dependency>
<groupId>org.tanukisoftware</groupId>
<artifactId>wrapper</artifactId>
<version>3.3.5</version>
<scope>runtime</scope>
</dependency>
</dependencies>
Avvisi nel rapporto di costruzione:
[assembly:directory {execution: make-assembly}]
Reading assembly descriptor: assembly.xml
Processing DependencySet (output=/lib)
[WARNING] The following patterns were never triggered in this artifact exclusion filter:
o 'org.tanukisoftware:wrapper:exe:3.3.5'
Processing DependencySet (output=/bin)
[WARNING] The following patterns were never triggered in this artifact inclusion filter:
o 'org.tanukisoftware:wrapper:exe:3.3.5'
Soluzione
Non so se questo sarà d'aiuto, ma quello che faccio sempre è nel pom del genitore mettere le dipendenze in un blocco di gestione delle dipendenze; ??
<dependencyManagement>
<!-- dependencies with exclusions -->
<dependencies>
<dependency>
<groupId>org.springframework</groupId>
<artifactId>spring-aop</artifactId>
<version>${version.springframework}</version>
<exclusions>
<exclusion>
<groupId>commons-logging</groupId>
<artifactId>commons-logging</artifactId>
</exclusion>
</exclusions>
</dependency>
Quindi, nel riquadro figlio, elenca nuovamente le dipendenze, ma senza la versione e le esclusioni
<dependencies>
<dependency>
<groupId>org.springframework</groupId>
<artifactId>spring-aop</artifactId>
</dependency>
Ma ad essere sinceri, per il mio primo e unico montaggio, non sono riuscito a farlo funzionare in un modulo figlio e inserirlo nel pom del genitore. Ecco il mio file assembly, per creare un file zip per un programma java autonomo, gestito da cron:
<?xml version="1.0" encoding="UTF-8"?>
<assembly>
<id>${project.layer}-both</id>
<formats>
<format>zip</format>
</formats>
<includeBaseDirectory>false</includeBaseDirectory>
<baseDirectory>/</baseDirectory>
<moduleSets>
<moduleSet>
<includes>
<include>edu.berkeley.ist.cars:cars_upload</include>
</includes>
<binaries>
<unpack>false</unpack>
<useStrictFiltering>true</useStrictFiltering>
<includeDependencies>true</includeDependencies>
<outputDirectory>upload</outputDirectory>
</binaries>
</moduleSet>
<moduleSet>
<includes>
<include>edu.berkeley.ist.cars:cars_download</include>
</includes>
<binaries>
<unpack>false</unpack>
<useStrictFiltering>true</useStrictFiltering>
<includeDependencies>true</includeDependencies>
<outputDirectory>download</outputDirectory>
</binaries>
</moduleSet>
</moduleSets>
<!--
crontab.txt is put in twice, in both upload and download, just in case.
-->
<files>
<!-- upload files -->
<file>
<source>src/stuff/scripts/cars_upload.sh</source>
<lineEnding>unix</lineEnding>
<filtered>true</filtered>
<outputDirectory>upload</outputDirectory>
</file>
<file>
<source>src/stuff/notes/crontab-${project.layer}.txt</source>
<destName>crontab.txt</destName>
<lineEnding>unix</lineEnding>
<filtered>true</filtered>
<outputDirectory>upload</outputDirectory>
</file>
<!-- download files -->
<file>
<source>src/stuff/scripts/cars_download.sh</source>
<lineEnding>unix</lineEnding>
<filtered>true</filtered>
<outputDirectory>download</outputDirectory>
</file>
<file>
<source>src/stuff/notes/crontab-${project.layer}.txt</source>
<destName>crontab.txt</destName>
<lineEnding>unix</lineEnding>
<filtered>true</filtered>
<outputDirectory>download</outputDirectory>
</file>
</files>
</assembly>
Esistono due directory di livello superiore nel file zip, upload e download.