[ 
https://issues.apache.org/jira/browse/SCM-365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17961145#comment-17961145
 ] 

ASF GitHub Bot commented on SCM-365:
------------------------------------

jira-importer commented on issue #574:
URL: https://github.com/apache/maven-scm/issues/574#issuecomment-2964604806

   **[Michael 
Osipov](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=michael-o)**
 commented
   
   This issue has been auto closed because it has been inactive for a long 
period of time. If you think this issue still applies, retest your problem with 
the most recent version of Maven and the affected component, reopen and post 
your results.
   




> <includes> and <excludes> do not seem to work correctly during scm:checkin
> --------------------------------------------------------------------------
>
>                 Key: SCM-365
>                 URL: https://issues.apache.org/jira/browse/SCM-365
>             Project: Maven SCM (Moved to GitHub Issues)
>          Issue Type: Bug
>          Components: maven-scm-provider-cvs
>    Affects Versions: 1.0
>            Reporter: njones
>            Priority: Major
>
> I am trying to use the scm plugin automatically during Maven builds.  My real 
> goal for this is to check only one file back in, but no matter what I try, 
> the plugin checks in ANY file that has been changed.  Below is one 
> configuration that I have tried.
> <plugin>
>    <groupId>org.apache.maven.plugins</groupId>
>    <artifactId>maven-scm-plugin</artifactId>
>    <version>1.0</version>
>    <inherited>false</inherited>
>    <executions>
>       <execution>
>          <phase>process-resources</phase>
>          <goals>
>             <goal>checkin</goal>
>          </goals>
>          <configuration>
>             <excludes>**/**</excludes>
>             <includes>version.properties</includes>
>          </configuration>
>       </execution>
>    </executions>
> </plugin>
> I also tried using only the <includes> tag without excluding anything, but it 
> did not work either.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to