commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stefan Bodewig <bode...@apache.org>
Subject Re: [compress] Planning for a 1.3 Release?
Date Mon, 17 Oct 2011 14:16:23 GMT
On 2011-10-11, Gary Gregory wrote:

> On Tue, Oct 11, 2011 at 11:21 AM, Stefan Bodewig <bodewig@apache.org> wrote:

>> On 2011-10-11, Gary Gregory wrote:

>>> On Tue, Oct 11, 2011 at 10:20 AM, Stefan Bodewig <bodewig@apache.org>
>> wrote:

>>>> One thing that we may or may not want to address are the integration
>>>> tests for Zip64 which are currently only run when the run-it profile is
>>>> enabled.  These tests need some zips generated by other tools that are
>>>> currently not part of svn and we discussed publishing them as separate
>>>> artifacts - personally I wouldn't even know where to start for this.

>>> I am not in favor of code all over the place, it should all be in the
>>> project, whether or not or when it is run is a different story.

>>> If these are data/resource files, why not put them in a resource jar in
>>> MC?

>> By "put them in a resource jar in MC" you mean I'd assemble a single jar
>> file commons-compress-testresources-1.0.jar that contains all those zips
>> and publish it, right?

> Yep. Because third party programs were used to create the files, they
> should be saved somewhere.

> We have two options:

> (1) SVN is not acceptable it seems. Could SVN even handle a giant file?

The individual files are between 4.5MB and 15MB each.  We are talking
about the ZIPs in <http://people.apache.org/~bodewig/commons-compress/>
and five of those attached to
<https://issues.apache.org/jira/browse/COMPRESS-36>.  Not exactly huge
but too big to have them i trunk IMHO.

> (2) That leaves some place that the build can handle downloading and caching
> automatically, which is what Maven and Ivy are good at doing.

I created
<http://svn.apache.org/repos/asf/commons/proper/compress/test-resources/>
which holds the POM for such a test-resources artifact.  I copied the
eleven archives used during the tests into src/main/resources and ran
"mvn package" and something surprising happened.  The resulting jar is
5MB in size.  I.e. we have one of the very rare cases where compressing
a ZIP with ZIP reduces the archive size considerably because it still
contains lots of redundant data.

How do I proceed?  Upload the jar and pom to Nexus (pgp signed, of
course) and call for a vote?

Stefan

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org


Mime
View raw message