You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Michael Osipov (JIRA)" <ji...@apache.org> on 2018/12/27 23:44:00 UTC
[jira] [Closed] (SCM-777) Maven plugin's scm:validate ignores
scmCheckWorkingDirectoryUrl configuration in favor of system property
[ https://issues.apache.org/jira/browse/SCM-777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Osipov closed SCM-777.
------------------------------
Resolution: Cannot Reproduce
Fix Version/s: (was: waiting-for-feedback)
No reaction for months.
> 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
> Priority: Major
>
> 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}
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-scm-plugin</artifactId>
> <configuration>
> <scmCheckWorkingDirectoryUrl>true</scmCheckWorkingDirectoryUrl> <!-- this configuration is ignored, don't know why -->
> </configuration>
> <executions>
> <execution>
> <phase>validate</phase>
> <configuration>
> <scmCheckWorkingDirectoryUrl>true</scmCheckWorkingDirectoryUrl> <!-- neither does this -->
> </configuration>
> <goals>
> <goal>validate</goal>
> </goals>
> </execution>
> </executions>
> </plugin>
> {code}
> *Workaround:* Use <systemProperty> section. Tried <systemPropertyVariables> and for some reason that didn't appear to work.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)