[ 
https://jira.codehaus.org/browse/SCM-388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=297081#comment-297081
 ] 

Chris Graham commented on SCM-388:
----------------------------------

Does that mean that this issue can be closed?

                
> scm:clearcase:load ..... should support more than one loadrule
> --------------------------------------------------------------
>
>                 Key: SCM-388
>                 URL: https://jira.codehaus.org/browse/SCM-388
>             Project: Maven SCM
>          Issue Type: Improvement
>          Components: maven-scm-provider-clearcase
>    Affects Versions: 1.0-beta-3
>         Environment: Windows XP, Maven 2.0.9
>            Reporter: Torsten Reinhard
>
> With auto-generated configSpecs actually there is a limitation:
> ...
> Specify one load rule for the project you want to check out within the SCM URL
> ...
> In many cases, more than one loadRule would be very useful - this will also 
> prevent from moving modules from one directory to another, just for having 
> them all under one parent-directory for scm:goal purposes.
> Therefore specifying 
> scm:clearcase:load /MY_VOB/my/project/dir, load /MY_VOB/my/project/dir2, load 
> /MY_VOB/my/project/dir3 ....
> could be an idea? 
> The fix for that is just a StringTokenizer in the method
>     protected String createConfigSpec( String loadDirectory, ScmVersion 
> version )
>     {
>         ....
>         // TODO replace this with a StringTokenizer
>         configSpec.append( "load " + loadDirectory + "\n" );
>         return configSpec.toString();
>     }
> at 
> org.apache.maven.scm.provider.clearcase.command.checkout.ClearCaseCheckOutCommand
>  
> Can anyone do that little enhancement?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to