From issues-return-131920-archive-asf-public=cust-asf.ponee.io@maven.apache.org Fri Apr 27 08:58:04 2018 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id 21FA3180608 for ; Fri, 27 Apr 2018 08:58:03 +0200 (CEST) Received: (qmail 98925 invoked by uid 500); 27 Apr 2018 06:58:03 -0000 Mailing-List: contact issues-help@maven.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@maven.apache.org Delivered-To: mailing list issues@maven.apache.org Received: (qmail 98911 invoked by uid 99); 27 Apr 2018 06:58:03 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 27 Apr 2018 06:58:03 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 95BAFCA6B8 for ; Fri, 27 Apr 2018 06:58:02 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -110.301 X-Spam-Level: X-Spam-Status: No, score=-110.301 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, USER_IN_DEF_SPF_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id y-ZWXlB_o_6b for ; Fri, 27 Apr 2018 06:58:01 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 63DEB5F39F for ; Fri, 27 Apr 2018 06:58:01 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id ABD21E0DF9 for ; Fri, 27 Apr 2018 06:58:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 2DD5324254 for ; Fri, 27 Apr 2018 06:58:00 +0000 (UTC) Date: Fri, 27 Apr 2018 06:58:00 +0000 (UTC) From: "James Z.M. Gao (JIRA)" To: issues@maven.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (MNG-6392) Add Project Settings .mvn/settings.xml MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/MNG-6392?page=3Dcom.atlassian.= jira.plugin.system.issuetabpanels:all-tabpanel ] James Z.M. Gao updated MNG-6392: -------------------------------- Description:=20 Maven originally have two settings slots, user and global. But the project = need and should have more ability to control how itself built by maven. Jus= t follow the core-extension way, we can add a new settings slot, project se= ttings at=C2=A0 =C2=A0 {code:java} ${maven.multiModuleProjectDirectory}/.mvn/settings.xml{code} =C2=A0 =C2=A0 Then the settings merge order from high priority to low is * project level * user level * global level This order is widely used in many projects such as git. =C2=A0 h2. Special fields in projects settings {{servers.server[].configuration}}=C2=A0will be merged deeply, and prefer o= nes in project settings. Some fields should be controlled only by the user, not any project, so they= are always ignored and copied back from user or global level settings: * localRepository * interactiveMode * offline * usePluginRegistry * proxies * servers.server[].\{username,password,privateKey,passphrase,filePermissio= ns,directoryPermissions} =C2=A0 =C2=A0 With this feature, many things become easy.=C2=A0When we developing multipl= y projects from different organizations/companies/envrionments, the maven c= onfigurations may conflict, and are annoying to manage (edit manually or us= e some switch scripts each time we switch the project or environment). Anot= her problem is when using some corp maven repositories or mirros for bootst= raping the team common=C2=A0root poms or core-extensions, the developers ha= ve to do some setup actions. But the projects should be `mvn verify`-ed out= of box. =C2=A0 Here is a [fast implementation via core-extension|https://github.com/gzm55/= project-settings-maven-extension], but this feature should woks before load= ing extensions. was: Maven originally have two settings slots, user and global. But the project = need and should have more ability to control how itself built by maven. Jus= t follow the core-extension way, we can add a new settings slot, project se= ttings at=C2=A0 =C2=A0 {code:java} ${maven.multiModuleProjectDirectory}/.mvn/settings.xml{code} =C2=A0 =C2=A0 Then the settings merge order from high priority to low is * project level * user level * global level This order is widely used in many projects such as git. In the project settings, we should always ignore some=C2=A0_personal local_= =C2=A0fields, including localRepository,=C2=A0interactiveMode,=C2=A0offline= and=C2=A0usePluginRegistry. =C2=A0 With this feature, many things become easy.=C2=A0When we developing multipl= y projects from different organizations/companies/envrionments, the maven c= onfigurations may conflict, and are annoying to manage (edit manually or us= e some switch scripts each time we switch the project or environment). Anot= her problem is when using some corp maven repositories or mirros for bootst= raping the team common=C2=A0root poms or core-extensions, the developers ha= ve to do some setup actions. But the projects should be `mvn verify`-ed out= of box. =C2=A0 Here is a [fast implementation via core-extension|https://github.com/gzm55/= project-settings-maven-extension], but this feature should woks before load= ing extensions. > Add Project Settings .mvn/settings.xml > -------------------------------------- > > Key: MNG-6392 > URL: https://issues.apache.org/jira/browse/MNG-6392 > Project: Maven > Issue Type: New Feature > Components: Bootstrap & Build, Settings > Affects Versions: 3.5.3 > Reporter: James Z.M. Gao > Priority: Major > > Maven originally have two settings slots, user and global. But the projec= t need and should have more ability to control how itself built by maven. J= ust follow the core-extension way, we can add a new settings slot, project = settings at=C2=A0 > =C2=A0 > {code:java} > ${maven.multiModuleProjectDirectory}/.mvn/settings.xml{code} > =C2=A0 > =C2=A0 > Then the settings merge order from high priority to low is > * project level > * user level > * global level > This order is widely used in many projects such as git. > =C2=A0 > h2. Special fields in projects settings > {{servers.server[].configuration}}=C2=A0will be merged deeply, and prefer= ones in project settings. > Some fields should be controlled only by the user, not any project, so th= ey are always ignored and copied back from user or global level settings: > * localRepository > * interactiveMode > * offline > * usePluginRegistry > * proxies > * servers.server[].\{username,password,privateKey,passphrase,filePermiss= ions,directoryPermissions} > =C2=A0 > =C2=A0 > With this feature, many things become easy.=C2=A0When we developing multi= ply projects from different organizations/companies/envrionments, the maven= configurations may conflict, and are annoying to manage (edit manually or = use some switch scripts each time we switch the project or environment). An= other problem is when using some corp maven repositories or mirros for boot= straping the team common=C2=A0root poms or core-extensions, the developers = have to do some setup actions. But the projects should be `mvn verify`-ed o= ut of box. > =C2=A0 > Here is a [fast implementation via core-extension|https://github.com/gzm5= 5/project-settings-maven-extension], but this feature should woks before lo= ading extensions. -- This message was sent by Atlassian JIRA (v7.6.3#76005)