Mailing-List: contact issues-help@maven.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@maven.apache.org
Date: Mon, 31 Oct 2016 20:14:59 +0000 (UTC)
From: "Plamen Totev (JIRA)" <jira@apache.org>
To: issues@maven.apache.org
Message-ID: <JIRA.13010442.1475842920000.136326.1477944899911@Atlassian.JIRA>
In-Reply-To: <JIRA.13010442.1475842920000@Atlassian.JIRA>
References: <JIRA.13010442.1475842920000@Atlassian.JIRA> <JIRA.13010442.1475842920337@arcas>
Subject: [jira] [Commented] (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: Mon, 31 Oct 2016 20:15:02 -0000


    [ https://issues.apache.org/jira/browse/MASSEMBLY-833?page=3Dcom.atlass=
ian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D1=
5623230#comment-15623230 ]=20

Plamen Totev commented on MASSEMBLY-833:
----------------------------------------

[~gboue], just to mention that the archivers themselves can add  finalizers=
(and some of them are adding real not virtual files). For example {{Abstrac=
tArchiver}} adds {{DotDirectiveArchiveFinalizer}} if {{dotFileDirectory}} i=
s set. {{DotDirectiveArchiveFinalizer#getVirtualFiles}} returns empty list =
because it adds real files (directories stored in {{.plxarc}}) file. So I'm=
 not completely sure if there is reliable method outside {{AbstractArchiver=
}} to check if the archive is going to be empty.=20

Of course since the assembly plugin have quite a lot of control over the {{=
Archiver}} configuration I guess it's safe to say there are no added extra =
finalizers apart the ones added by the plugin itself. I just wanted to ment=
ion that just in case :)

> 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
>         Attachments: _MASSEMBLY_833__added_ignoreNoFiles_parameter_allowi=
ng_not_to_fail_when_there_are_no_files.patch
>
>   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 are no files to package see=
ms like reasonable solution?


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