[
https://issues.apache.org/jira/browse/SCM-136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17964317#comment-17964317
]
Olivier Lamy commented on SCM-136:
----------------------------------
This project has moved from Jira to GitHub Issues. This issue was migrated to
[apache/maven-scm#404|https://github.com/apache/maven-scm/issues/404].
> Make it possible to pay attention to .cvsrc
> --------------------------------------------
>
> Key: SCM-136
> URL: https://issues.apache.org/jira/browse/SCM-136
> Project: Maven SCM (Moved to GitHub Issues)
> Issue Type: Improvement
> Components: maven-scm-provider-cvs
> Affects Versions: 1.0-beta-2
> Reporter: Matthew Beermann
> Assignee: Emmanuel Venisse
> Priority: Major
> Fix For: 1.0-beta-3
>
>
> There ought to be a way to tell the SCM plugin to obey the .cvsrc file.
> Here's why:
> I've had developers complain about empty directories showing up in their jar
> endstates. Simple, I thought - just add "checkout -P" to my .cvsrc file. But,
> if I'm reading
> http://svn.apache.org/viewcvs.cgi/maven/scm/trunk/maven-scm-providers/maven-scm-provider-cvs/src/main/java/org/apache/maven/scm/provider/cvslib/command/checkout/CvsCheckOutCommand.java?view=markup
> correctly, the plugin will always ignore the .cvsrc file since it always
> specifies the "-f" flag and doesn't allow arbitrary flags to be passed in.
> I can understand the reasoning behind this behavior - there are certainly CVS
> flags that would make Maven very unhappy - but there's also something to be
> said for giving people enough rope to hang themselves with. All sorts of
> important/useful settings (like compression) could be in their .cvsrc too. In
> my case, at least, I don't see any other way to get it done.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
