[ 
https://jira.codehaus.org/browse/SCM-777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mark Herman updated SCM-777:
----------------------------

    Description: 
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.

  was:
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}


> Maven plugin's scm:validate ignores configuration in favor of system property
> -----------------------------------------------------------------------------
>
>                 Key: SCM-777
>                 URL: https://jira.codehaus.org/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}
> <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
(v6.1.6#6162)

Reply via email to