10. jan. 2015 15:19 skrev "Jason van Zyl" <ja...@takari.io>:

> So I took a look and my feedback:
>
> You have a blurb about how to use the parallel code in commons-compress
> but there is no test or example that actually shows how to make one. The
> actual working example is in plexus-archiver and if you don't mind I'd like
> to put a utility in commons-compress so that users can easily utilize the
> code. Basically "use this number of threads and you go make it faster".
> Something like the ConcurrentJarCreator but general purpose, and that
> utility can probably be used, with instruction from the user, to do the
> work in parallel. It would be really nice just to weave the code into the
> existing code paths so users just get the benefit with an upgrade.
>

I originally had ConcurrentJarCreator in my c-compress fork. We discussed
this (arguably somewhat briefly) on the commons mailing list and to my
understanding Stefan wants c-c to be more of a toolkit (at a slightly lower
level) and did not want this in c-compress. So now it's in
plexus-archiver.  Although one could argument for something like
ConcurrentJarCreator in a maven-shared jar file. But it's not going to help
much as long as p-archiver is the client all out plugins uses. You could
always argue on the commons mailing list that something CJC-like should be
part of c-c

It does not blend into existing code paths, and it's not going to happen on
my shift for legitimate technical reasons.

Maven users get the benefit with a straight upgrade of a dependency.

C'est la vie.

Kristian


On Jan 10, 2015, at 7:23 AM, Kristian Rosenvold <
> kristian.rosenv...@gmail.com> wrote:
>
> > I just released plexus-archiver version 2.10-beta-1 to maven central.
> >
> > This is a "technology preview" of the multithreaded Zip feature I have
> > been adding to commons-compress for the last few weeks, and will
> > basically use all available CPU cores when compressing the archive.
> >
> > To test/use this feature, you can add the following clause some plugins:
> >
> > <plugin>
> >  <groupId>org.apache.maven.plugins</groupId>
> >  <artifactId>maven-assembly-plugin</artifactId>
> >  <version>2.5.3</version>
> >  <dependencies>
> >    <dependency>
> >      <groupId>org.codehaus.plexus</groupId>
> >      <artifactId>plexus-archiver</artifactId>
> >      <version>2.10-beta-1</version>
> >    </dependency>
> >    <dependency>
> >      <groupId>org.codehaus.plexus</groupId>
> >      <artifactId>plexus-io</artifactId>
> >      <version>2.4.1</version>
> >    </dependency>
> >  </dependencies>
> > </plugin>
> >
> > This applies to maven-war-plugin, maven-jar-plugin, maven-ear-plugin,
> > maven-assembly-plugin, maven-dependency-plugin and probably a few
> > others too.
> >
> > The feature is basically "done". commons-compress 1.10 has not yet
> > been released, and the moment this happens there will be a non-beta
> > version of plexus-archiver. This version contains a shaded-snapshot
> > version of commons-compress.
> >
> > Please note that if your project basically produces a 30K jar file,
> > there is not much to be expected from this upgrade. The larger your
> > zip/jar/ear/war files, the more you can expect. And, of course, you
> > can use this as an argument towards your boss to get a 6 core CPU.
> >
> > Feedback appreciated !
> >
> > In other news, the java 1.6 version "3.0" was also released today,
> > which contains "snappy" compression. 3.0 does not yet contain the
> > parallel feature.
> >
> >
> > Kristian
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > For additional commands, e-mail: dev-h...@maven.apache.org
> >
>
> Thanks,
>
> Jason
>
> ----------------------------------------------------------
> Jason van Zyl
> Founder,  Apache Maven
> http://twitter.com/jvanzyl
> http://twitter.com/takari_io
> ---------------------------------------------------------
>
> A language that doesn’t affect the way you think about programming is not
> worth knowing.
>
>  -- Alan Perlis
>
>
>
>
>
>
>
>
>
>

Reply via email to