[
https://issues.apache.org/jira/browse/SCM-121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17960217#comment-17960217
]
ASF GitHub Bot commented on SCM-121:
------------------------------------
jira-importer commented on issue #353:
URL: https://github.com/apache/maven-scm/issues/353#issuecomment-2964589031
**[Dennis
Lundberg](https://issues.apache.org/jira/secure/[email protected])**
commented
I am experiencing this as well. My environment is Windows XP using cvsnt as
my command-line client.
Mike wrote about this error on the dev-list:
org.apache.maven.scm.provider.cvslib.command.checkout.CvsCheckoutCommandTest
junit.framework.AssertionFailedError: expected:<38403> but was:<39511>
at junit.framework.Assert.fail(Assert.java:47)
at junit.framework.Assert.failNotEquals(Assert.java:282)
at junit.framework.Assert.assertEquals(Assert.java:64)
at junit.framework.Assert.assertEquals(Assert.java:136)
at junit.framework.Assert.assertEquals(Assert.java:142)
at
org.apache.maven.scm.provider.cvslib.command.checkout.CvsCheckoutCommandTest.testCheckOutWithTag(CvsCheckoutCommandTest.java:88)
After some investigation I have concluded that this happens in a Windows
environment because the command-line cvs client checks out the file with
windows line-endings (CR LF). This makes the total size of the file in bytes
larger than it would in a unix environment. That is what the error above is
telling us.
I googled and found the CVS-book at
http://cvsbook.red-bean.com/cvsbook.html#CVS%20is%20not%20doing%20line-end%20conversion%20correctly
They seem to imply that the only way of stopping a cvs client from
converting line-endings to the native sort is to say that the file is binary.
That would mean specifying -kb in the CVS/Entries file. So I tried this and
created such a directory and file in the test repository, but the results were
the same.
I am trying to make improvements to the cvs provider but I'm having all
sorts of trouble just building maven-scm, being on Windows and not having a
default locale of English. It's quite frustrating.
To move forward, SCM-10 talks about switching from command line cvs to
cvslib. This would be a major improvement for compatibility. There is a gotcha
that cvslib might not support the ext transport. If that is the case, do you
think it would be possible to use command line cvs for ext transport and cvslib
for the rest?
> Intermittent CVS test failures
> ------------------------------
>
> Key: SCM-121
> URL: https://issues.apache.org/jira/browse/SCM-121
> Project: Maven SCM (Moved to GitHub Issues)
> Issue Type: Bug
> Components: maven-scm-provider-cvs
> Affects Versions: 1.0-beta-3
> Reporter: Mike Perham
> Priority: Major
> Attachments: cvs.exe
>
>
> Dan and I continue to have test failures when trying to compile the cvs
> plugin in our environment. I emailed these problems to the scm-dev list
> about a week ago.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
