incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mark Struberg <>
Subject Re: [DISCUSS] json as new incubator project
Date Sun, 01 Jun 2014 10:29:56 GMT

commons might be an option. But we still would need to go through the incubator. 
Otoh Commons proved not to be very JSR friendly to be honest. We had this discussion for BVal
etc, and recent JCS discussions where also not in favour for it. I'd be happy to host it over
there though. 

Christian, txs for bringing up noggit. Didn't even know it. How far is it away from the SOLR
version? And to which degree does it cover JSON? Anyone who knows the SOLR code think we could
split this out form SOLR if this version is better?

Romains code is pretty good already. But it uses antlr for parsing. Not sure how much this
is a blocker when it comes to performance tuning and cutting down the size of the JAR yet.


On Sunday, 1 June 2014, 10:47, Christian Grobmeier <> wrote:

>On 1 Jun 2014, at 0:31, Justin Mclean wrote:
>> Hi,
>>> About the name any proposition is welcomed. I though to "brace" BTW.
>> Apache Argonaut sounds good but I assume that name is in common use so 
>> perhaps Argus (the ship builder), or perhaps Fleece?
>I actually once wrote an article called "Json and the golden fleece" 
>(just in german),
>so I would like this reference too.
>I was a little bit involved in that JSR (not very active to be honest) 
>and developed
>a JSON component myself before the JSR was in the making, so I have an 
>interest in it.
>Unfortunately I have very limited time to help actively. Anyway if there 
>is trouble
>to finding an additional mentor, I will step up.
>On the proposal i see two sections called "initial committers" and one 
>"core developer". I would like to suggest to remove the section "core 
>developer" and on of the "initial committers" blocks.
>I would like to also suggest to look into Noggit:
>which is more or less used in a later form in Solr.
>As sponsoring entity it might even make sense to look at Apache Commons, 
>as the component will be small.
>It would also relax the naming problem, as it would most likely be named 
>Apache Commons Json then.
>> Thanks,
>> Justin
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail:
>> For additional commands, e-mail:
>The Zen Programmer:
>GPG: 0xA5CC90DB
>To unsubscribe, e-mail:
>For additional commands, e-mail:
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message