Mailing-List: contact issues-help@continuum.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@continuum.apache.org
Received-SPF: pass (athena.apache.org: local policy)
Message-ID: 
 <2700455.1219686267793.JavaMail.haus-jira@codehaus01.managed.contegix.com>
Date: Mon, 25 Aug 2008 12:44:27 -0500 (CDT)
From: "David Greenberg (JIRA)" <jira@codehaus.org>
To: issues@continuum.apache.org
Subject: [jira] Created: (CONTINUUM-1852) NFS lock on pom during release
 causes error
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

NFS lock on pom during release causes error
-------------------------------------------

                 Key: CONTINUUM-1852
                 URL: http://jira.codehaus.org/browse/CONTINUUM-1852
             Project: Continuum
          Issue Type: Bug
          Components: Core system, Release
    Affects Versions: 1.1
         Environment: I am on Solaris 8, but this is probably a generic issue.  This is with Continuum as a webapp in a Tomcat 6 instance.  The SCM is SVN.
            Reporter: David Greenberg
            Priority: Minor


Often when I prepare a release for a project, the process fails when checking for local modifications.  This failure is triggered by a .nfs file in the working directory (the working directory is on an NFS server).  Usually, I can get past this after a few tries, but that isn't really an ideal solution.  Could Continuum be set to ignore these files as local modifications?  I can add them to the SVN ignore file, but that is more of a hack than a long-term solution, as it would need to be applied to every package.  Ideally, Continuum would be able to use fuser to determine that it, or the server hosting it, owns the lock.  I know this is platform dependent, and I'm not sure if there are some pure Java tools out there to assist with this.

-- 
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