On Mon, Aug 5, 2013 at 10:20 AM, Branko Čibej <br...@wandisco.com> wrote:
>>> The better option of course is to just use the JavaHL API instead. >> I have seen this problem as well. We have a Java server application >> that scripts the command line so that it can retrieve and accept the >> SSL certificate. We added the new --force-interactive option but the >> problem is that the prompting seems to happen in the process that >> started the Java server application instead of in the application >> itself. So it is no longer possible to capture the command line output >> with the certificate details and accept it. > > It has nothing to do with processes. We prompt the terminal, and read > responses from the terminal, instead of using stderr for the prompt and > stdin for the response. Note that on Windows, this was always the case > for certain kinds of prompts. 1.8 merely makes that consistent. > >> Personally, I think this is a regression and not an improvement. > > You had a year and a half to raise this on dev@. :) When the changes were made I just assumed Java apps would still work. I assumed the code would just see the JVM as being the terminal. I also generally trust the dev team to not introduce regressions. Guess I was wrong on both counts. -- Thanks Mark Phippard http://markphip.blogspot.com/
