Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 9F713200CF8 for ; Tue, 15 Aug 2017 11:13:07 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 9C4B2166618; Tue, 15 Aug 2017 09:13:07 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id ED6A6166632 for ; Tue, 15 Aug 2017 11:13:06 +0200 (CEST) Received: (qmail 73840 invoked by uid 500); 15 Aug 2017 09:13:05 -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 73524 invoked by uid 99); 15 Aug 2017 09:13:03 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 15 Aug 2017 09:13:03 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id EFFA8180236 for ; Tue, 15 Aug 2017 09:13:02 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -99.202 X-Spam-Level: X-Spam-Status: No, score=-99.202 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id WLtQowoEoq4W for ; Tue, 15 Aug 2017 09:13:02 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 5F2B45F239 for ; Tue, 15 Aug 2017 09:13: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 A2754E028F for ; Tue, 15 Aug 2017 09:13: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 41E0F2140C for ; Tue, 15 Aug 2017 09:13:00 +0000 (UTC) Date: Tue, 15 Aug 2017 09:13:00 +0000 (UTC) From: "Andreas Schaller (JIRA)" To: issues@maven.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (SCM-777) Maven plugin's scm:validate ignores scmCheckWorkingDirectoryUrl configuration in favor of system property MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Tue, 15 Aug 2017 09:13:07 -0000 [ https://issues.apache.org/jira/browse/SCM-777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16126979#comment-16126979 ] Andreas Schaller commented on SCM-777: -------------------------------------- In ValidateMojo, the field that gets the configuration value injected is described as unused: {code:java} @Parameter( property = "scmCheckWorkingDirectoryUrl", defaultValue = "false" ) // Actually unused in the code here. Present for doc purpose, // see org.apache.maven.scm.provider.svn.AbstractSvnScmProvider.CHECK_WORKING_DIRECTORY_URL private boolean scmCheckWorkingDirectoryUrl; {code} In the validateConnection-method however, the field is used to store the current working directory as system property. Wouldn't it be sufficient to also store the value of scmCheckWorkingDirectoryUrl as system propety at this point so that it can be used in AbstractSvnScmProvider? Not nice but should work > Maven plugin's scm:validate ignores scmCheckWorkingDirectoryUrl configuration in favor of system property > --------------------------------------------------------------------------------------------------------- > > Key: SCM-777 > URL: https://issues.apache.org/jira/browse/SCM-777 > Project: Maven SCM > Issue Type: Bug > Components: maven-plugin > Affects Versions: 1.9.1 > Environment: Java 7 x64 on Windows 7 > Reporter: Mark Herman > > org.apache.maven.scm.manager.AbstractScmManager.checkWorkingDirectoryUrl() uses... {code} Boolean.getBoolean( CHECK_WORKING_DIRECTORY_URL ) {code} ...in order to check if it should check the repository on scm:validate. This will only react to the system property, and not to the maven configuration. > *Result:* no maven config will enable the check working directory option, only passing it in as a jvm argument. > *Expected:* this should work: > {code} > > org.apache.maven.plugins > maven-scm-plugin > > true > > > > validate > > true > > > validate > > > > > {code} > *Workaround:* Use section. Tried and for some reason that didn't appear to work. -- This message was sent by Atlassian JIRA (v6.4.14#64029)