Hi Romain,
I guess you are assuming that pipeline options are flat command line like
argument, right ?
Actually, theoretically, pipeline options can be represented as json, that's
why we use jackson.
The pipeline options can be serialized/deserialized as json.
The purpose is to remove the jackson dependencies ?
Regards
JB
On 01/07/2018 11:38 AM, Romain Manni-Bucau wrote:
Hi guys,
not sure i fully get why jackson is used to parse pipeline options in the
testing integration
why not using a token parser like [1] which allows to map 1-1 with the user
interface (command line) the options?
[1]
https://github.com/Talend/component-runtime/blob/master/component-server/src/main/java/org/talend/sdk/component/server/lang/StringPropertiesTokenizer.java
Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> | Blog
<https://rmannibucau.metawerx.net/> | Old Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau>
--
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
