|
If you were logged in you would be able to see more operations.
|
|
|
QuickBuild
Created: 14/Nov/17 12:48 PM
Updated: 24/Feb/18 03:23 AM
|
|
| Component/s: |
None
|
| Affects Version/s: |
None
|
| Fix Version/s: |
8.0.0
|
|
|
Original Estimate:
|
1 day
|
Remaining Estimate:
|
1 day
|
Time Spent:
|
Unknown
|
|
|
It's not possible actually to parse command standard output using a specific encoding.
If two tools encode standard output with different character sets, it's not possible to decode properly the command out.
* Add parse log charset property into command steps
* By default this charset shall be the JVM default charset
* Charset selection shall be defined as text input to be able to include non standard charsets
|
|
Description
|
It's not possible actually to parse command standard output using a specific encoding.
If two tools encode standard output with different character sets, it's not possible to decode properly the command out.
* Add parse log charset property into command steps
* By default this charset shall be the JVM default charset
* Charset selection shall be defined as text input to be able to include non standard charsets |
Show » |
| No work has yet been logged on this issue.
|
|
Improvement
Closed
Major
Provide the possibility to define an encoding on parsing command stdout