[
https://issues.apache.org/jira/browse/SHINDIG-1124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12734347#action_12734347
]
Chris Chabot commented on SHINDIG-1124:
---------------------------------------
The main point of creating a JIRA issue is for legal reasons, by *attaching a
patch* to this issue and checking "I hereby grant the ASF rights to.. " we can
accept that code without endangering the status of the project. By just
including the link you haven't formally given us permission to use it in Apache
Shindig.
Now I know this gets confusing because there are people who use codereviews
only, but these are all project committers who have either signed the
individual or corp Contributes License Agreement which covers this already.
Anyhow, in short: Could you please attach that patch to this issue please? (See
"Attach File" on the left). Thanks!
> Upgrade to caja r3574
> ---------------------
>
> Key: SHINDIG-1124
> URL: https://issues.apache.org/jira/browse/SHINDIG-1124
> Project: Shindig
> Issue Type: Bug
> Components: Java
> Reporter: Jasvir Nagra
>
> * removes libs=caja from url params in sample container - the behavior for
> this
> appears to have changed in shindig
> * changes to CajaContentRewriter to ensure error messages from caja are
> properly
> escaped
> * changes to CajaContentRewriter to handle the new static html output
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
