Mailing-List: contact issues-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: issues@commons.apache.org
Date: Thu, 6 Nov 2014 06:12:34 +0000 (UTC)
From: "Kristian Rosenvold (JIRA)" <jira@apache.org>
To: issues@commons.apache.org
Message-ID: <JIRA.12747210.1412917621000.431922.1415254354024@Atlassian.JIRA>
In-Reply-To: <JIRA.12747210.1412917621000@Atlassian.JIRA>
References: <JIRA.12747210.1412917621000@Atlassian.JIRA>
 <JIRA.12747210.1412917621194@arcas>
Subject: [jira] [Commented] (COMPRESS-290)
 TarArchiveOutputStream#failForBigNumber could be more helpful
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/COMPRESS-290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14199863#comment-14199863 ] 

Kristian Rosenvold commented on COMPRESS-290:
---------------------------------------------

It took us just a couple of days to get https://jira.codehaus.org/browse/MASSEMBLY-728, so I think I'll nudge a patch for this somewhat up on my priorities :)

> TarArchiveOutputStream#failForBigNumber could be more helpful
> -------------------------------------------------------------
>
>                 Key: COMPRESS-290
>                 URL: https://issues.apache.org/jira/browse/COMPRESS-290
>             Project: Commons Compress
>          Issue Type: Improvement
>            Reporter: Kristian Rosenvold
>
> We have now ported all of maven to use commons compress. When a user is running tar compression, we may sometimes fail because the selected tar format does not support big numbers.
> In this context we'd like to help our users by informing them that there may be other tar formats than can be more suitable. I would request that this method throw some specialized subclass of RuntimeException that we can catch to identify this particular error condition, so we can talk to our users about their options :)


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