Hi,
IMHO it makes perfect sense to add this to Sling - either to the bundles
or the contrib area.
But I don't necessairily want copy the source into our repository. So I
see the following options:
* Invite James Wiltshire join Sling with the project (might not
be an option for him or his employer, though the license alone
is promising ;-) )
* Have James Wiltshire add OSGi Manifest headers to his library
and deploy it to a Maven repository. So we can just reference
it from Sling as we do with Groovy.
* Create a wrapper project including the library (easier if it would
be available from Maven, but doable if just downloading from
Sourceforge, similar as we do with Dojo)
Opinions ?
Regards
Felix
Am 21.09.2010 16:44, schrieb Róbert Csákány (JIRA):
>
> [
> https://issues.apache.org/jira/browse/SLING-1792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
> ]
>
> Róbert Csákány updated SLING-1792:
> ----------------------------------
>
> Attachment: jsp-taglib-json.zip
>
> I've attached the source code of the bundle. It's utilize James Wiltshire's
> Json library - (http://json-taglib.sourceforge.net).
>
> It's tested and works.
>
>> JSP Json Taglib
>> ---------------
>>
>> Key: SLING-1792
>> URL: https://issues.apache.org/jira/browse/SLING-1792
>> Project: Sling
>> Issue Type: New Feature
>> Components: Scripting
>> Reporter: Róbert Csákány
>> Attachments: jsp-taglib-json.zip
>>
>>
>> Providing Json taglig support for JSP taglib
>
