You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@continuum.apache.org by "David Greenberg (JIRA)" <ji...@codehaus.org> on 2008/08/25 19:44:27 UTC
[jira] Created: (CONTINUUM-1852) NFS lock on pom during release
causes error
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
[jira] Closed: (CONTINUUM-1852) NFS lock on pom during release
causes error
Posted by "Emmanuel Venisse (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/CONTINUUM-1852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Emmanuel Venisse closed CONTINUUM-1852.
---------------------------------------
Assignee: Emmanuel Venisse
Resolution: Won't Fix
Continuum doesn't have to define which files are or not in the project.
It is better to add your file in svn:ignore svn property
> 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
> Assignee: Emmanuel Venisse
> 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