I agree that having a set of official extensions might be ideal.
Today the most popular are still the Takari ones AFAIK but they aren't
officially supported by our team and thus probably less used than they
could/should.
Due to the git organization @ASF I don't know what is easier between having
1 repo or several ones.
In general I prefer to have 1 repo = 1 lifecycle (the opposite of monorepo)
but maybe it could have some sense in the long term and some shared code
... not sure.


On Tue, Dec 7, 2021 at 9:53 AM Tamás Cservenák <ta...@cservenak.net> wrote:

> Howdy,
>
> I'd rather group ASF extensions (are there any existing ones aside of
> caching?),
> to be clear... so GH repo could be something like
> apache/maven-caching-extension
> apache/maven-foobar-extension
> etc?
>
> T
>
> On Tue, Dec 7, 2021 at 9:48 AM Guillaume Nodet <gno...@apache.org> wrote:
>
> > Following the recent work done to integrate the maven caching /
> incremental
> > build system into maven, I think it's now time to discuss where we want
> its
> > long-term location to be.
> >
> > This extension was donated a few months ago and provides local and remote
> > caching of maven project's output, based on computed hashes of the
> inputs.
> > It's defined as a maven extension and can be used as a core or build
> > extension.  This avoids building the project and speeds up builds a lot !
> >
> > The current status of this work resides in 3 branches:
> >   * MNG-7129-3.8.x (PR at https://github.com/apache/maven/pull/622)
> >   * MNG-7129-master (PR at https://github.com/apache/maven/pull/607)
> >   * https://github.com/apache/maven/tree/MNG-7129-maven-caching
> > The two first PRs include the required changes to integrate the extension
> > in maven 3.8.x (or rather 3.9.x) and in master. The last branch is the
> one
> > that should be moved to a separate repository and contain the code for
> the
> > extension.  The goal is to agree on the location and the final name for
> the
> > repository (it can't be changed easily).
> >
> > I propose maven-caching as the repository / subproject name, but any
> better
> > name is welcomed of course.
> >
> > --
> > ------------------------
> > Guillaume Nodet
> >
>


-- 
Arnaud Héritier
Twitter/GitHub/... : aheritier

Reply via email to