Awesome, thx a ton Hervé ! Le sam. 15 janv. 2022 à 19:01, Herve Boutemy <[email protected]> a écrit :
> Jira project created and issues moved: old issues like > https://issues.apache.org/jira/browse/MNG-7129 will automatically > redirect to their new location > > issue https://issues.apache.org/jira/browse/MNG-7391 created to track the > addition of API to Maven core that is required for Build Cache extension, > with associated PRs for Maven 3.8.x and Maven 4 > We'll need review to merge these PRs for the next Maven releases to be > able to support the extension > > Documentation published to > https://maven.apache.org/extensions/maven-build-cache-extension/ > > I think this extension starts to be in a reasonable state for Maven devs > to test: next key step will be MNG-7391 PRs merged and Maven releases done > > Regards, > > Hervé > > On 2022/01/13 09:55:01 Maximilian Novikov wrote: > > Thanks a lot Herve, well done on moving the extension to a new repo. > > > > >> (1) ok if I delete MNG-7129-maven-caching branch from maven.git? > > +1, ok > > > > >> (2) ok for me to create MBUILDCACHE Jira project? > > +1 > > > > >>(3) ok for me to move MNG-7129 issue (and sub-tasks) to that new Jira > project? > > Mb, copy or clone ? as #607 and #622 are done under this Jira > > > > Kind regards, > > Max > > > > -----Original Message----- > > From: Hervé BOUTEMY <[email protected]> > > Sent: Tuesday, January 11, 2022 2:17 AM > > To: Maven Developers List <[email protected]> > > Subject: Re: [DISCUSS] Move maven caching to an external repository > > > > let's finish the work > > > > code of former MNG-7129-maven-caching branch is now in > https://github.com/apache/maven-build-cache-extension > > > > (1) ok if I delete MNG-7129-maven-caching branch from maven.git? > > > > (2) ok for me to create MBUILDCACHE Jira project? > > > > (3) ok for me to move MNG-7129 issue (and sub-tasks) to that new Jira > project? > > > > (4) I tried to rebase MNG-7129-3.8.x, but it was not ok: please rebase > (to avoid future merge commit) > > > > (5) https://github.com/apache/maven/pull/607 requires some rework and > rebase on top of master to become mergeable > > > > (6) for (4) and (5), define if the new API should be tracked with > MNG-7129 or if another MNG issue should be defined (= what I suppose) > > > > (7) update Maven 3 and Maven 4 submodules link in > https://github.com/apache/ maven-build-cache-extension to match previous > updates > > > > > > I don't know what will remain after that for a release, but at least, > we'll be in a clean situation > > > > Regards > > > > Hervé > > > > Le mardi 7 décembre 2021, 09:47:12 CET Guillaume Nodet a écrit : > > > 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. > > > > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] For additional > commands, e-mail: [email protected] > > > > > > > > --- > > This e-mail may contain confidential and/or privileged information. If > you are not the intended recipient (or have received this e-mail in error) > please notify the sender immediately and delete this e-mail. Any > unauthorized copying, disclosure or distribution of the material in this > e-mail is strictly forbidden. > > > > Please refer to https://www.db.com/disclosures for additional EU > corporate and regulatory disclosures and to > http://www.db.com/unitedkingdom/content/privacy.htm for information about > privacy. > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- ------------------------ Guillaume Nodet
