Re: reviewing Maven Wrapper before releasing
Everything builds and it generates the wrapper for a project in a way will be familiar to existing users. The switch for current users should, hopefully, be painless and transparent. Nice work Robert and Hervé. I put a notice on the GitHub page for the Takari version about the impending release at Apache, and provided pointers to the new Git repository and JIRA project. jvz > On Dec 6, 2021, at 6:07 PM, Hervé BOUTEMY wrote: > > Hi, > > Maven Wrapper has been donated to Apache Maven, imported to > https://github.com/apache/maven-wrapper > > Documentation published to https://maven.apache.org/wrapper/ > > Here is the list of fixes from previous 0.5.6 release: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12323721&version=12350068 > > > Please test and review so we can do a release soon > > Regards, > > Hervé > > > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [DISCUSS] Move maven caching to an external repository
Le mardi 7 décembre 2021, 10:21:47 CET Arnaud Héritier a écrit : > I agree that having a set of official extensions might be ideal. see https://maven.apache.org/extensions/ We can publish maven-caching-extension to https://maven.apache.org/extensions/maven-caching-extension I can publish the site tonight it's really like plugins > 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. creating one Git repository per project is easy, no problem: once we have the name, creating the Git repository is just self-service for PMC done in 1 minute Regards, Hervé > > On Tue, Dec 7, 2021 at 9:53 AM Tamás Cservenák 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 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 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [DISCUSS] Move maven caching to an external repository
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 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 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
Re: [DISCUSS] Move maven caching to an external repository
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 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 >
[DISCUSS] Move maven caching to an external repository
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
