[jira] [Closed] (SCM-605) More logs when "Terminated with fatal signal 11" with CVS

["Michael Osipov (JIRA)" <ji...@apache.org>]

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

Michael Osipov closed SCM-605.
------------------------------
    Resolution: Auto Closed

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.

> More logs when "Terminated with fatal signal 11" with CVS
> ---------------------------------------------------------
>
>                 Key: SCM-605
>                 URL: https://issues.apache.org/jira/browse/SCM-605
>             Project: Maven SCM
>          Issue Type: Improvement
>          Components: maven-scm-provider-cvs
>    Affects Versions: 1.4
>         Environment: Windows & Unix
>            Reporter: Alix Lourme
>            Priority: Minor
>
> Some problems can affect the scm plugin but not other client (dos, eclipse).
> For exemple, a scm config : 
> {code}
> <build>
> 	<plugins>
> 		<plugin>
> 			<groupId>org.apache.maven.plugins</groupId>
> 			<artifactId>maven-scm-plugin</artifactId>
> 			<version>1.4</version>
> 			<configuration>
> 				<checkoutDirectory>target/projectTest</checkoutDirectory>
> 				<connectionUrl>scm:cvs:pserver:@myHost:/myDirectory/myProject:myModule</connectionUrl>
> 				<username>myUser</username>
> 				<password>myPassword</password>
> 			</configuration>
> 		</plugin>
> 	</plugins>
> </build>
> {code}
> Can crash with *mvn scm:checkout* :
> {code}
> [INFO] [scm:checkout {execution: default-cli}]
> [INFO] Removing C:\...\workspace_eclipse\Test\target\ProjectTest
> [INFO] Executing: cmd.exe /X /C "cvs -z3 -f -d :pserver:myUser@myHost:/myDirectory/myProject -q checkout -d ProjectTest myModule"
> [INFO] Working directory: C:\...\workspace_eclipse\Test\target
> [ERROR] Provider message:
> [ERROR] The cvs command failed.
> [ERROR] Command output:
> [ERROR] Terminated with fatal signal 11
> {code}
> The problem is CVS ... but the cause is very hard to diagnostic.
> In my case, it was a file of 100 Ko (cvs filesystem Unix), there wasn't problem with Eclipse's checkout or CVS bin (dos) checkout (same command as SCM use ... strange). 
> But there was some problem of commit on this file under Eclipse. 
> It's relativly easy to solve the problem when you have +the+ file :) ... but to find it, the only way is :
> # SCM's  checkout : signal 11 ... so you have not all files
> # CVS bin checkout with output saving to have the order of project files
> # Make a script doing directory comparaison and have the first file who doesn't exist in SCM checkout.
> A CVS bin write log :
> {code}
> U myProject/myPackage/File1.java
> U myProject/myPackage/File2.java
> ...
> {code}
> For each file, I don't know if this log is displayed before of after getting file, but when scm crash, it would be nice to have the last log line ...
> * If the CVS log is printed before getting file, it's the bad file => nice
> * If the CVS log is printed after getting file, the message could be "Problem getting file after : 'U project/[the precedent file who was ok]'"
> _And sorry for my worse english_



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)