maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alix Lourme (JIRA)" <j...@codehaus.org>
Subject [jira] Created: (SCM-605) More logs when "Terminated with fatal signal 11" with CVS
Date Thu, 10 Feb 2011 16:00:22 GMT
More logs when "Terminated with fatal signal 11" with CVS
---------------------------------------------------------

                 Key: SCM-605
                 URL: http://jira.codehaus.org/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 is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message