maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Martin Vehovský (JIRA) <j...@apache.org>
Subject [jira] [Updated] (MASSEMBLY-833) Ability to ignore errors about no files to package in assembly
Date Fri, 07 Oct 2016 12:33:20 GMT

     [ https://issues.apache.org/jira/browse/MASSEMBLY-833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Martin Vehovský updated MASSEMBLY-833:
--------------------------------------
    Description: 
Motivation: Having extremely large multi-module project, some modules lets call them "application"
modules provide "configuration" files, and they provide them for different environments. Problem
is that not all "application" modules provide "configuration" files for all environments.
In case there are no files available for assembly, the single goal ends up with ERROR:

Failed to
 create assembly: Error creating assembly archive <assembly_name>: You must set at least
one file.


Available workaround is to specify a property to by default skip the assembly execution and
only if there are files for given environment set this property to not skip the given assembly
execution.

However for large number of environments this solution starts to be messy and hard to maintain.


Do you think that having assembly Parameter "ignoreNoFiles" that will cause to skip the archive
creation for cases there aro no files to package seems like reasonable solution?


  was:
Motivation: Having extremely large multi-module project, some modules lets call them "application"
modules provide "configuration" files, and they provide them for different environments. Problem
is that not all "application" modules provide "configuration" files for all environments.
In case there are no files available for assembly, the single goal ends up with ERROR:

Failed to
 create assembly: Error creating assembly archive <assembly_name>: You must set at least
one file.


Available workaround is to specify a property to by default skip the assembly execution and
only if there are files for given environment set this property to not skip the given assembly
execution.

However for large number of environments this solution starts to be messy and hard to maintain.


Having assembly Parameter "ignoreNoFiles" that will cause to skip the archive creation for
cases there aro no files to package seems like reasonable solution.



> Ability to ignore errors about no files to package in assembly
> --------------------------------------------------------------
>
>                 Key: MASSEMBLY-833
>                 URL: https://issues.apache.org/jira/browse/MASSEMBLY-833
>             Project: Maven Assembly Plugin
>          Issue Type: Improvement
>    Affects Versions: 2.6
>            Reporter: Martin Vehovský
>   Original Estimate: 4h
>  Remaining Estimate: 4h
>
> Motivation: Having extremely large multi-module project, some modules lets call them
"application" modules provide "configuration" files, and they provide them for different environments.
Problem is that not all "application" modules provide "configuration" files for all environments.
In case there are no files available for assembly, the single goal ends up with ERROR:
> Failed to
>  create assembly: Error creating assembly archive <assembly_name>: You must set
at least one file.
> Available workaround is to specify a property to by default skip the assembly execution
and only if there are files for given environment set this property to not skip the given
assembly execution.
> However for large number of environments this solution starts to be messy and hard to
maintain.
> Do you think that having assembly Parameter "ignoreNoFiles" that will cause to skip the
archive creation for cases there aro no files to package seems like reasonable solution?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message