[kepler-dev] [Bug 4311] Build system appears to lock if there is a conflict upon update

[bugzilla-daemon at ecoinformatics.org]

http://bugzilla.ecoinformatics.org/show_bug.cgi?id=4311

--- Comment #5 from David Welker <welker4kepler at gmail.com> 2010-01-07 20:12:01 PST ---
Are you saying that when the update failed to complete, it did not say why?
That is unusual. Can you reproduce this error and share the output that you
get?

Normally, when an error occurs updating (for example, due to a lock) it is
quite clear what caused the problem. For example, as referenced in bug 4281,
when the "ant update" does not complete due to a lock, you get an error that
explains why:

===========
[update-modules] Updating ptolemy-lib...
[update-modules] svn -r head update c:\tmp\cxh\src\kepler\ptolemy-lib 
[update-modules] At revision 20190.
[update-modules] 
[update-modules] svn -r head update c:\tmp\cxh\src\kepler\build-area 
[update-modules] svn: Working copy 'c:\tmp\cxh\src\kepler\build-area' locked
[update-modules] svn: run 'svn cleanup' to remove locks (type 'svn help
cleanup' for details)
[update-modules] 
[update-modules] WARNING: It appears that the command did not execute properly
and exited with an exit code of: 1
===========

If you can reproduce this issue and verify that in fact the conflict does not
show up in output, I will look into it more. Otherwise, the solution is to fix
the problem manually and run "ant update" again.

-- 
Configure bugmail: http://bugzilla.ecoinformatics.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.