Description
While working through a large multi-module project I discovered a custom Assembly Descriptor file. What I don't fully understand is the following, especially the includes
section.
<assembly [...]>
[...]
<dependencySets>
<dependencySet>
<scope>provided</scope>
<unpack>true</unpack>
<unpackOptions>
<includes>
<include>defaults*.properties</include>
</includes>
</unpackOptions>
<outputFileNameMapping>
${artifact.artifactId}
</outputFileNameMapping>
<includes>
<include>${project.groupId}:[project]-settings</include>
</includes>
</dependencySet>
</dependencySets>
[...]
</assembly>
The assembly documentation describes the include
section as a "file and/or directory pattern for matching items to be included from an archive as it is unpacked".
The includes
property documentation of dependencySet
states the following:
If none is present, then represents all valid values.
Question
Does include
work exclusively? Can I therefore expect only the defaults*.properties
to be regarded as provided
(according to this particular section)?
How do unpackOptions-includes
interfer with the basic includes
(last section of dependencySet
)?