Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

System I/O is not out available from non-Container-based classloaders when running in a Container. #33

Closed
brianoliver opened this issue May 21, 2013 · 3 comments
Closed

System I/O is not out available from non-Container-based classloaders when running in a Container. #33

brianoliver opened this issue May 21, 2013 · 3 comments
Assignees
@brianoliver
Labels
Module: Runtime Priority: Major
Milestone
1.0.0

Comments

@brianoliver
Copy link
Contributor

We noticed that due to earlier cleanup / refactoring of the Container streams I/O is no longer output from JUnit tests when running in Container Mode.

This is due to the "default" scope using the new ContainerScope implementation, that of which captures and pipes output. This is incorrect behavior for the "default" scope, which should instead send I/O directly to the Platform Scope.
@brianoliver
Copy link
Contributor Author

Reported by @brianoliver

@brianoliver
Copy link
Contributor Author

Marked as fixed by @brianoliver on Tuesday, May 21st 2013, 11:22:02 am

@brianoliver
Copy link
Contributor Author

This issue was imported from JIRA ORACLETOOLS-33

@brianoliver brianoliver self-assigned this May 16, 2016
@brianoliver brianoliver added this to the 1.0.0 milestone May 16, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@brianoliver brianoliver

Labels
Module: Runtime Priority: Major
Projects
None yet
Milestone
1.0.0
Development

No branches or pull requests
1 participant
@brianoliver