Mailing-List: contact dev-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Commons Developers List" <dev@commons.apache.org>
Received-SPF: pass (athena.apache.org: domain of garydgregory@gmail.com
 designates 74.125.83.54 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAOGo0Vb_OWOnMd_XtfkOvb_5r+aHh9Dqc6=xQh13=UZdZqh6Cw@mail.gmail.com>
References: <87ha7jcil2.fsf@v35516.1blu.de>
	<CACZkXPwY2kdZELnim1Y=D84ioMD3OJx2Erm2hjgPSCG6A1uSdQ@mail.gmail.com>
	<CAOGo0Vb_OWOnMd_XtfkOvb_5r+aHh9Dqc6=xQh13=UZdZqh6Cw@mail.gmail.com>
Date: Fri, 28 Feb 2014 12:48:26 -0500
Message-ID: 
 <CACZkXPyE05wdDG3Xg6jFYRjtvUiqCH5PP6sgi1cu_3ickcZ8tg@mail.gmail.com>
Subject: Re: [compress] problems with 7z BCJ methods
From: Gary Gregory <garydgregory@gmail.com>
To: Commons Developers List <dev@commons.apache.org>
Content-Type: multipart/alternative; boundary=f46d0415532c7f90b704f37b0b98

--f46d0415532c7f90b704f37b0b98
Content-Type: text/plain; charset=UTF-8

Do we have any idea WRT a new release of XZ?

Gary


On Fri, Feb 28, 2014 at 12:33 PM, sebb <sebbaz@gmail.com> wrote:

> On 28 February 2014 17:02, Gary Gregory <garydgregory@gmail.com> wrote:
> > On Fri, Feb 28, 2014 at 11:23 AM, Stefan Bodewig <bodewig@apache.org>
> wrote:
> >
> >> Hi,
> >>
> >> I've managed to implement the major BCJ filters for 7z (special filters
> >> for native executables) by simply invoking the XZ for Java
> >> implementations for it.  This is needed for  COMPRESS-257.
> >>
> >> Unfortunately there is a bug in XZ for Java that has already been fixed
> >> in git.  When using a released version of XZ together wirh Compress
> >> 1.8-SNAPSHOT you'll be greeted with an AssertionError thrown from inside
> >> XZ as soon as you try to read an archive that uses BCJ.
> >>
> >> I see two options and I'm not quite sure which is better from a user's
> >> POV:
> >>
> >> * document the problem in XZ so people know they'll need to upgrade XZ
> >>   once it becomes available - and deal with recurring questions about
> >>   AssertionErrors
> >>
> >
> > I like this one because we can document it and then the user can just
> drop
> > in a new XZ. Otherwise you'd need BOTH XZ and [compress] to have a new
> > release.
>
> Can Compress catch the specific Assertion Error and convert it to a
> message that explains the issue?
> Perhaps even provide a link to a Wiki FAQ?
>
> Alternatively, can Compress detect the XZ version and refuse to run
> BCJ, again with suitable message?
>
> These work-rounds can eventually be removed.
>
> > Gary
> >
> >
> >>
> >> * back out the BCJ code and re-introduce it once XZ has seen a new
> >>   release - this way users get a "method not supported" error rather
> >>   than some strange AssertionError
> >>
> >> Stefan
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> >> For additional commands, e-mail: dev-help@commons.apache.org
> >>
> >>
> >
> >
> > --
> > E-Mail: garydgregory@gmail.com | ggregory@apache.org
> > Java Persistence with Hibernate, Second Edition<
> http://www.manning.com/bauer3/>
> > JUnit in Action, Second Edition <http://www.manning.com/tahchiev/>
> > Spring Batch in Action <http://www.manning.com/templier/>
> > Blog: http://garygregory.wordpress.com
> > Home: http://garygregory.com/
> > Tweet! http://twitter.com/GaryGregory
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>


-- 
E-Mail: garydgregory@gmail.com | ggregory@apache.org
Java Persistence with Hibernate, Second Edition<http://www.manning.com/bauer3/>
JUnit in Action, Second Edition <http://www.manning.com/tahchiev/>
Spring Batch in Action <http://www.manning.com/templier/>
Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory

--f46d0415532c7f90b704f37b0b98--