Bug 1444620 - (6.4.z) CLI returns always "0" if CLI is started with "cmd /c " on Windows
Summary: (6.4.z) CLI returns always "0" if CLI is started with "cmd /c " on Windows
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: CLI
Version: 6.4.14
Hardware: Unspecified
OS: Windows
unspecified
unspecified
Target Milestone: CR3
: EAP 6.4.15
Assignee: Petr Jurak
QA Contact: Peter Mackay
URL:
Whiteboard:
Depends On:
Blocks: eap6415-payload
TreeView+ depends on / blocked
 
Reported: 2017-04-23 11:08 UTC by Petr Jurak
Modified: 2017-05-19 08:06 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Windows
Last Closed: 2017-05-19 08:06:20 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker JBEAP-10313 0 Critical Verified (7.1.0) CLI returns always "0" if CLI is started with "cmd /c " on Windows 2017-09-18 10:45:30 UTC
Red Hat Issue Tracker JBEAP-10482 0 Critical Verified (7.0.z) CLI returns always "0" if CLI is started with "cmd /c " on Windows 2017-09-18 10:45:30 UTC
Red Hat Issue Tracker WFCORE-2667 0 Critical Resolved CLI returns always "0" if CLI is started with "cmd /c " on Windows 2017-09-18 10:45:30 UTC

Description Petr Jurak 2017-04-23 11:08:04 UTC 
CLI returns always "0" if CLI is started with "cmd /c " on Windows.

This issue is regression.
Comment 3 Peter Mackay 2017-05-15 21:51:00 UTC 
Verified with EAP 6.4.15.CP.CR3
Comment 4 Petr Penicka 2017-05-19 08:06:20 UTC 
Released on May 18 as part of EAP 6.4.15.
Note You need to log in before you can comment on or make changes to this bug.