maven-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mirko Friedenhagen <mfriedenha...@gmail.com>
Subject Re: Fail assembly plugin if symbols are unknown
Date Sat, 08 Mar 2014 08:57:01 GMT
Bernd,

what about using enforcer's requireProperty rule?

Regards
Mirko
-- 
Sent from my mobile
On Mar 7, 2014 10:20 PM, "Bernd Eckenfels" <ecki@zusammenkunft.net> wrote:

> 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
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message