Hello,
we use in a lot of projects special assembly descriptors, which
typically use the following pattern:
<assembly
...
<id>distribution</id>
<baseDirectory></baseDirectory>
<files>
<file>
<outputDirectory>${dist.x}/${dist.base.software.lib}</outputDirectory>
<source>${project.build.directory}/x.jar</source>
</file>
</files>
</assembly>
We are currently cleaning up some POMs and there is a risk that some of
the properties are no longer defined. This produces ZIP files which
have directory or file names in there with unexpanded ${dist*} symbols
(file name not filters).
Is it possible to make the assembly (archiver?) plugin (and
others) fail in a situation where ${} cannot be interpolated?
The same would be nice for manifest headers in the maven archiver
(filter in this case)?
Greetings
Bernd
we use in a lot of projects special assembly descriptors, which
typically use the following pattern:
<assembly
...
<id>distribution</id>
<baseDirectory></baseDirectory>
<files>
<file>
<outputDirectory>${dist.x}/${dist.base.software.lib}</outputDirectory>
<source>${project.build.directory}/x.jar</source>
</file>
</files>
</assembly>
We are currently cleaning up some POMs and there is a risk that some of
the properties are no longer defined. This produces ZIP files which
have directory or file names in there with unexpanded ${dist*} symbols
(file name not filters).
Is it possible to make the assembly (archiver?) plugin (and
others) fail in a situation where ${} cannot be interpolated?
The same would be nice for manifest headers in the maven archiver
(filter in this case)?
Greetings
Bernd