Apex CLI editor closes standard input/output/error

The Apex CLI editor closes its input and output when it completes. This is correct behaviour when the input and output are files. However, if the input and output are tied to standard input, output, and error then if there are subsequent actions in the JVM (Such as continuing to run Apex as we do in tests), then any output such as logging is lost.

This fix checks for standard input/output/error before closing the input
and output.

Issue-ID: POLICY-2897
Change-Id: Ifa20b62511f770197f30c4a817212a92876dd6a6
Signed-off-by: liamfallon <liam.fallon@est.tech>
1 file changed
tree: 1175bd21681b98d9e4a7575323bf4ca0b1660511
  1. auth/
  2. context/
  3. core/
  4. examples/
  5. model/
  6. packages/
  7. plugins/
  8. releases/
  9. services/
  10. testsuites/
  11. tools/
  12. .gitignore
  13. .gitreview
  14. docker_build.sh
  15. docker_merge.sh
  16. docker_verify.sh
  17. INFO.yaml
  18. LICENSE.txt
  19. pom.xml
  20. README.md
  21. version.properties
README.md

Copyright (C) 2016-2018 Ericsson. All rights reserved. This file is licensed under the CREATIVE COMMONS ATTRIBUTION 4.0 INTERNATIONAL LICENSE Full license text at https://creativecommons.org/licenses/by/4.0/legalcode

This source repository contains the ONAP Policy APEX PDP Engine code. The settings file only needs to support the standard Maven repositories (e.g. central = http://repo1.maven.org/maven2/), and any proxy settings needed in your environment.

To build it using Maven 3, run: mvn clean install