maven-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Hervé BOUTEMY <herve.bout...@free.fr>
Subject Re: Incremental build API
Date Wed, 26 Mar 2014 02:31:33 GMT
Hi Jason,

Interesting.

What is the plan about org.sonatype.plexus:plexus-build-api already integrated 
in some plugins?

Given the expected large diffusion of this API, wouldn't it be wise to put it 
at Apache?
or Eclipse?
(I won't rehash previous discussions about freedom and preferences from each 
people)

Regards,

Hervé

Le mardi 25 mars 2014 10:43:57 Jason van Zyl a écrit :
> Hi,
> 
> For those who are interested in incremental builds we, at Takari, have
> released a general purpose incremental build API with an initial focus on
> Maven. We've created a short, high-level description of the framework[1]
> and we've opened up our Git repository with the code[2]. We also have a
> some demos that people can look at[3]. We are, and have been, running this
> code in production for a few months but it is still a work in progress. We
> have implemented a Maven lifecycle that integrates this API but we've just
> started using it ourselves. We will open this lifecycle up shortly for
> people to try but for now, if you're interested in incremental builds take
> a look and let us know what you think!
> 
> A note to those interested that the use of the API in Maven requires 3.2.1+.
> 
> [1]: http://takari.io/2014/03/25/incremental-build.html
> [2]: https://github.com/takari/io.takari.incrementalbuild
> [3]:
> https://github.com/takari/io.takari.incrementalbuild/tree/master/incrementa
> lbuild/src/test/java/io/takari/incremental/demo
> 
> Thanks,
> 
> Jason
> 
> ----------------------------------------------------------
> Jason van Zyl
> Founder,  Apache Maven
> http://twitter.com/jvanzyl
> http://twitter.com/takari_io
> ---------------------------------------------------------
> 
> People develop abstractions by generalizing from concrete examples.
> Every attempt to determine the correct abstraction on paper without
> actually developing a running system is doomed to failure. No one
> is that smart. A framework is a resuable design, so you develop it by
> looking at the things it is supposed to be a design of. The more examples
> you look at, the more general your framework will be.
> 
>   -- Ralph Johnson & Don Roberts, Patterns for Evolving Frameworks


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


Mime
View raw message