[JBoss JIRA] (ISPN-12074) Test progress messages are split over multiple lines
by Ryan Emerson (Jira)
[ https://issues.redhat.com/browse/ISPN-12074?page=com.atlassian.jira.plugi... ]
Ryan Emerson resolved ISPN-12074.
---------------------------------
Fix Version/s: 12.0.0.Dev01
(was: 12.0.0.Final)
(was: 11.0.2.Final)
Assignee: Dan Berindei
Resolution: Done
> Test progress messages are split over multiple lines
> ----------------------------------------------------
>
> Key: ISPN-12074
> URL: https://issues.redhat.com/browse/ISPN-12074
> Project: Infinispan
> Issue Type: Bug
> Components: Build, Test Suite
> Affects Versions: 11.0.1.Final
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Priority: Minor
> Fix For: 12.0.0.Dev01
>
>
> The {{System.out}} that {{TestSuiteProgress}} captures in its constructor is broken, and will split the output from a {{printf("a%sb")}} call over 3 lines.
> This happens since the upgrade to Maven Surefire 3.0.0-M4, and the issue is present in M5 as well.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 5 months
[JBoss JIRA] (ISPN-11724) CLI: Allow key and value encoding to be specified
by Ryan Emerson (Jira)
[ https://issues.redhat.com/browse/ISPN-11724?page=com.atlassian.jira.plugi... ]
Ryan Emerson reassigned ISPN-11724:
-----------------------------------
Assignee: (was: Ryan Emerson)
> CLI: Allow key and value encoding to be specified
> -------------------------------------------------
>
> Key: ISPN-11724
> URL: https://issues.redhat.com/browse/ISPN-11724
> Project: Infinispan
> Issue Type: Enhancement
> Components: CLI
> Affects Versions: 11.0.0.Dev04
> Reporter: Ryan Emerson
> Priority: Major
>
> The CLI allows {{put}} operations to specify the encoding of an entry via the {{--encoding}} flag, however this only applies to the value and a plain text key must be provided. For example:
> {code}
> put --encoding=application/json --file=example.json example
> {code}
> It should be possible for the key and values encoding to be specified like so:
> {code}
> cache put --key-encoding=application/json --value-encoding=application/json --file=example.json "example"
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 5 months
[JBoss JIRA] (ISPN-11725) CLI: Allow encoding to be set per cache context
by Ryan Emerson (Jira)
[ https://issues.redhat.com/browse/ISPN-11725?page=com.atlassian.jira.plugi... ]
Ryan Emerson reassigned ISPN-11725:
-----------------------------------
Assignee: (was: Ryan Emerson)
> CLI: Allow encoding to be set per cache context
> -----------------------------------------------
>
> Key: ISPN-11725
> URL: https://issues.redhat.com/browse/ISPN-11725
> Project: Infinispan
> Issue Type: Enhancement
> Components: CLI
> Affects Versions: 11.0.0.Dev04
> Reporter: Ryan Emerson
> Priority: Major
>
> Currently in the CLI it's necessary to set encoding per entry. It should be able to set the encoding per the context of the currently selected cache to reduce verbosity in batch files. For example:
> {code}
> cd cache/example
> cache put --key-encoding=application/json --value-encoding=application/json --file=example1.json "example1"
> cache put --key-encoding=application/json --value-encoding=application/json --file=example2.json "example2"
> {code}
> Can be simplified to:
> {code}
> cd cache/example
> set options --key-encoding=application/json --value-encoding=application/json
> cache put --file=example1.json "example1"
> cache put --file=example2.json "example2"
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 5 months