Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
cm.json-2.0.2
-
None
-
Important
Description
Currently, I updated the cm.json to 2.0.2 which cannot parse the existing configurator JSON files anymore.
For example:
{ "com.amitinside.gateway.sentry.hub" : { ":configurator:policy": "force", "type" : "runtime", "dsn" : "https://abc.com", "clientName" : "amit" } }
This cannot be parsed anymore after the update to 2.0.2 which used to work perfectly in 2.0.0. It always fails with Invalid JSON from bundle://XXXXXXX.
It fails exactly at the place where // is specified. The cm.json somehow detects // in URL values as comments.
Not sure though if it is fixed in 2.0.4. I can check when it will be published to the maven central.
Attachments
Issue Links
- is caused by
-
FELIX-6664 Comment Removing on JSONSupport MemoryInefficient
- Closed