Mailing-List: contact issues-help@maven.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@maven.apache.org
Date: Fri, 7 Oct 2016 12:33:20 +0000 (UTC)
From: =?utf-8?Q?Martin_Vehovsk=C3=BD_=28JIRA=29?= <jira@apache.org>
To: issues@maven.apache.org
Message-ID: <JIRA.13010442.1475842920000.762798.1475843600475@Atlassian.JIRA>
In-Reply-To: <JIRA.13010442.1475842920000@Atlassian.JIRA>
References: <JIRA.13010442.1475842920000@Atlassian.JIRA> <JIRA.13010442.1475842920337@arcas>
Subject: [jira] [Updated] (MASSEMBLY-833) Ability to ignore errors about no
 files to package in assembly
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
archived-at: Fri, 07 Oct 2016 12:33:28 -0000


     [ https://issues.apache.org/jira/browse/MASSEMBLY-833?page=3Dcom.atlas=
sian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Martin Vehovsk=C3=BD updated MASSEMBLY-833:
--------------------------------------
    Description:=20
Motivation: Having extremely large multi-module project, some modules lets =
call them "application" modules provide "configuration" files, and they pro=
vide 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 assemb=
ly execution and only if there are files for given environment set this pro=
perty to not skip the given assembly execution.

However for large number of environments this solution starts to be messy a=
nd 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 pro=
vide 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 assemb=
ly execution and only if there are files for given environment set this pro=
perty to not skip the given assembly execution.

However for large number of environments this solution starts to be messy a=
nd hard to maintain.


Having assembly Parameter "ignoreNoFiles" that will cause to skip the archi=
ve creation for cases there aro no files to package seems like reasonable s=
olution.


> 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=C3=BD
>   Original Estimate: 4h
>  Remaining Estimate: 4h
>
> Motivation: Having extremely large multi-module project, some modules let=
s call them "application" modules provide "configuration" files, and they p=
rovide them for different environments. Problem is that not all "applicatio=
n" modules provide "configuration" files for all environments. In case ther=
e are no files available for assembly, the single goal ends up with ERROR:
> Failed to
>  create assembly: Error creating assembly archive <assembly_name>: You mu=
st set at least one file.
> Available workaround is to specify a property to by default skip the asse=
mbly execution and only if there are files for given environment set this p=
roperty 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 cau=
se to skip the archive creation for cases there aro no files to package see=
ms like reasonable solution?


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