[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

Oliver Soong <soong at nceas.ucsb.edu> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |soong at nceas.ucsb.edu

--- Comment #4 from Oliver Soong <soong at nceas.ucsb.edu> 2010-01-07 19:57:51 PST ---
I'm not so sure it's a good idea to ignore this.  This happened to Mark,
Regetz, and me.  None of us had made any local changes, although I can't
remember exactly why there was a collision.  I think it was some config file
that had a default stored locally in the repository and changed when Kepler
started.  In any case, it was in no way clear whether, how, or why the build
was stalled.  A simple solution would be to pass stdin, stdout, and stderr to
the console.

I understand there's some complication to using stdin.  Maybe this will help
some: 
http://www.coderanch.com/t/419646/Ant-Maven-Other-Build-Tools/java-program-accept-user-input

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