From issues-return-100036-apmail-maven-issues-archive=maven.apache.org@maven.apache.org Thu Jan 22 22:48:44 2015 Return-Path: X-Original-To: apmail-maven-issues-archive@minotaur.apache.org Delivered-To: apmail-maven-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id BDB3C173BB for ; Thu, 22 Jan 2015 22:48:44 +0000 (UTC) Received: (qmail 11825 invoked by uid 500); 22 Jan 2015 22:48:44 -0000 Delivered-To: apmail-maven-issues-archive@maven.apache.org Received: (qmail 11771 invoked by uid 500); 22 Jan 2015 22:48:44 -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 11757 invoked by uid 99); 22 Jan 2015 22:48:44 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 22 Jan 2015 22:48:44 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [199.193.192.100] (HELO codehaus01.managed.contegix.com) (199.193.192.100) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 22 Jan 2015 22:48:19 +0000 Received: from codehaus01 (localhost.localdomain [127.0.0.1]) by codehaus01.managed.contegix.com (Postfix) with ESMTP id ED167B1166 for ; Thu, 22 Jan 2015 16:48:17 -0600 (CST) Date: Thu, 22 Jan 2015 16:48:17 -0600 (CST) From: "SebbASF (JIRA)" To: issues@maven.apache.org Message-ID: In-Reply-To: References: Subject: [jira] (MNGSITE-222) Incorrect statement regarding profiles activated with -P MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 22cf62d5d84cf5bea94eb3b65e0ebd09 X-Virus-Checked: Checked by ClamAV on apache.org [ https://jira.codehaus.org/browse/MNGSITE-222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=361674#comment-361674 ] SebbASF commented on MNGSITE-222: --------------------------------- That would be better, but it is then not clear what happens to profiles activated by other means. It might be better to change it to something like: When this option is specified, the profile(s) specified in the option argument will be activated in addition to any profiles which are activated by their activation configuration or the activeProfiles entry in settings.xml. Assuming that is true - I've not tested settings.xml > Incorrect statement regarding profiles activated with -P > -------------------------------------------------------- > > Key: MNGSITE-222 > URL: https://jira.codehaus.org/browse/MNGSITE-222 > Project: Maven Project Web Site > Issue Type: Bug > Environment: http://maven.apache.org/guides/introduction/introduction-to-profiles.html > Reporter: SebbASF > > Website as above says: > {quote} > Profiles can be explicitly specified using the -P CLI option. > This option takes an argument that is a comma-delimited list of profile-ids to use. When this option is specified, no profiles other than those specified in the option argument will be activated. > {quote} > The last sentence above is not true. > As proof, try the following: > {code} > mvn -f help:active-profiles -Papache-release > {code} > The output is > {code} > Active Profiles for Project 'org.apache:apache:pom:16': > The following profiles are active: > - apache-release (source: org.apache:apache:16) > - maven-3 (source: org.apache:apache:16) > {code} -- This message was sent by Atlassian JIRA (v6.1.6#6162)